As much as I hate to say this, I have to give up on 2.6.39 for now. I just don't have the time nor energy to fix this. I'm grateful for all your testing, but it's just going to have to go on hold and I'll have to support .38 kernels in the meantime until I have a revelation of some sort, or help from someone who also knows kernel internals.
2.6.39 mainline (no BFS or ck-patch) hangs for me anyway. Something to do with the clocksource. Could be that whatever changed there also affects your patches.ReplyDelete
Worry not, Con! This is just for fun, right? (Most) people will survive without the .39 kernel, as you will know exceptionally well. In the mean while we can anesthetize ourselves with .38, lrzip, and dreams of 3.0-bfs :DReplyDelete
Yes, don't worry! Thnx for all your work Con!ReplyDelete
But: this is why BFS should be included into mainline - time for a compile time plugin infrastructure of the mainline scheduler.
At the previous thread: Wasn't this mainly because of virtualbox? Then, someone should ask in the forums of virtualbox.org for help with BFS integration pointing to Cons previous blog entry. Shouldn't there be anyone interested in this matter? Especially if this only reveals some deeper mainline bug ...
+1 on thanks for all the great work. Love BFS!ReplyDelete
Despite Cons "I have to give up" - I see him working: Two new test patches today.ReplyDelete
I put the linux-image-2.6.39-ck1-1_2.6.39-ck1-1-10.00.Custom_amd64.deb on 2 different servers.ReplyDelete
1 - ADM64 1 core 2500 MHz
The assembly is stable, without a glitch
2 - 6 * AMD64 3400
Hung assembly, even when you reboot. On this server to downgrade linux-image-126.96.36.199-ck1-1_188.8.131.52-ck1-a-10.00.Custom_amd64.deb
Thanks. I didn't say I was giving up forever, just for now.ReplyDelete
Sometimes it is good go on a walk about from time to time. I can't tell you how many times I've walked away from a problem for a few days then suddenly come up with a solution. Thanks for everything you do. It is appreciated.ReplyDelete
Con simply should wait:ReplyDelete
I saw some very low level trivial candidate patches for coming 184.108.40.206 in the queue, I don't know for sure this will be relevant:
The above patches from Gregs stable queue are identical to patches meant for 2.6.38. I dont expect them to solve the issues for BFS-404.ReplyDelete
Just for the record I never had a better and more performant system, which reliable serves my purpose:
Gentoo 64bit experimental compiled using gcc-4.6.0 running Linux-2.6.39-ck1-bfs404 patched with some 20 stable-queue fixes.