On 08/14/2010 03:39 PM, C wrote:
On Sat, Aug 14, 2010 at 22:29, David C. Rankin wrote:
I'm working to build a krashdump kernel to troubleshoot:
http://bugzilla.novell.com/show_bug.cgi?id=628166
which I haven't had time to do until today -- hopefully it will expose whatever the nasty little bug in 2.6.34 is. I've had great luck with 2.6.35.1 from Arch, the 2.6.34 kernel there suffered from a similar lockup problem. The key here is to identify what the issue was so it doesn't propagate forward in the kernel and bite us again in 2.6.36 :p
That would be annoying if it crops up again. I haven't done any investigating to try and discover what it is that was fixed. A couple of days ago, someone mentioned here about some problem with that version which was a known issue... but I didn't read up on what he was talking about.
BTW, I'm on 2.6.35-19 from Kernel:Head on my main server, and it's been flawless.
C
That is good news. I'll provide a follow-up if we ever get to the bottom of what the issue with 2.6.34 is. My "guess" is that it is hardware mis-identification at the module load stage during boot. What complicates things is that with KMS, that can occur at two different times now. If the loaded code is called when the module is loaded -- you lockup on boot, but it the code is loaded by not called until later -- well, you lock up when it is called. I have had two different laptops affected/(infected) by 2.6.34 in two different linux distros exhibiting 2 different repeatable hardlocks. Both boxes have run 20+ kernels and it is only the 2.6.34 version that hardlocks. We will see if my "guess" bears any fruit later... -- 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org