Re: [arch-general] kernel26 2.6.34.2-1 ALSO hardlocks my box on boot?? [ Solved in .35 ]
On 08/03/2010 05:09 PM, David C. Rankin wrote: Guys, What do we need to do to get this fixed?? I have sent Andreas a message to reopen the bug for the reason The bug continues to hardlock my box on boot, but failing that -- what else do I need to do? Per Andreas suggestion, I loaded the .35-2 kernel from testing. My box will boot past the UTF-8 line and runs well. Also relevant to http://bugs.archlinux.org/task/20200, compiz now works the way it is supposed to in .35. What changes were there between 2.6.34 and 2.6.35 that could have caused this? I hate having an issue this severe that gets fixed without understanding what was broken in the first place. Tobias, anybody know what the candidate changes were? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
[arch-general] kernel26 2.6.34.2-1 ALSO hardlocks my box on boot??
Guys, I still have this problem where the changes to the kernel for kernel26 2.6.34 cause my box to hardlock on boot! It happens every time after the kernel has booted once after the initial build of the initramfs with mkinitcpio. It is frustrating has hell. I opened bug 20200 which was closed yesterday for some reason and this bug is NOT fixed. I am continuing to run on the LTS kernel which works fine, but whatever changes were made to the kernel between LTS and 2.6.34 introduced a bug that causes the boot process to hardlock my box at the message: Configuring console for UTF-8 mode I suspect the lockup actually occurs at the line or two before where it loads modules, but I haven't a clue how to determine exactly what is causing this? This is serious stuff, if it is causing my Toshiba laptop to hardlock on boot, it is going to catch others and ... having your box hardlock on boot is somewhat difficult to overlook. If it were not for the fact that I also loaded the LTS kernel and have an alternative to boot into, Arch Linux would not run on my laptop at all. What do we need to do to get this fixed?? I have sent Andreas a message to reopen the bug for the reason The bug continues to hardlock my box on boot, but failing that -- what else do I need to do? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Re: [arch-general] kernel26 2.6.34.2-1 ALSO hardlocks my box on boot??
On Tue, Aug 3, 2010 at 6:09 PM, David C. Rankin drankina...@suddenlinkmail.com wrote: what else do I need to do? out of curiousity have you tried building your own kernel and bisecting it? or mailing the lkml? -- Caleb Cushing http://xenoterracide.com
Re: [arch-general] kernel26 2.6.34.2-1 ALSO hardlocks my box on boot??
Am Tue, 03 Aug 2010 17:09:52 -0500 schrieb David C. Rankin drankina...@suddenlinkmail.com: Guys, I still have this problem where the changes to the kernel for kernel26 2.6.34 cause my box to hardlock on boot! It happens every time after the kernel has booted once after the initial build of the initramfs with mkinitcpio. It is frustrating has hell. I opened bug 20200 which was closed yesterday for some reason and this bug is NOT fixed. Bug reopened. You didn't gave an answer for some days. Please make sure to divide it into either KMS/module loading is broken or your Compiz is fucked up. As written in the bugreport I had to manually put all needed graphics related modules into the rc.conf file. Now it boots almost every time for me. You can boot with debug command in the kernel append line to get more feedback when modules get loaded. -Andy
Re: [arch-general] kernel26 2.6.34.2-1 ALSO hardlocks my box on boot??
On 08/03/2010 11:49 PM, Andreas Radke wrote: Bug reopened. You didn't gave an answer for some days. Please make sure to divide it into either KMS/module loading is broken or your Compiz is fucked up. As written in the bugreport I had to manually put all needed graphics related modules into the rc.conf file. Now it boots almost every time for me. You can boot with debug command in the kernel append line to get more feedback when modules get loaded. I apologize for not getting back sooner, but at times my real life calls and I have to push linux to the side for a week or two. I'll have a bit of time this week and next to help as much as I can. What I really need is a list of what I can get off my box to help track this down. Heck, I don't even mind configuring the router to get the smart folks in and giving an account if that would help. Since this bug occurs before logging is available, that makes it doubly-hard for me to know where to even begin with this one. I've already run tests with both configurations of KMS early/late and posted the results to the bug report, but what more I need to do is where I'm drawing a blank. I'll start with debug appended to the kernel line and post the results back at the bug report. We'll go from there. The big issue/mystery is why in the heck the box hardlocks on boot starting with the 2nd boot after initramfs is compiled. At least I know that is the issue that needs to be addressed first to find out where the bug is. I'm a great set of hands at the keyboard -- it's knowing what to type that's the problem :p Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
