On 11/03/2010 10:03 PM, Heiko Baums wrote: > Am Wed, 03 Nov 2010 20:57:35 -0500 > schrieb "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>: > >> I think that is exactly the understanding I got from Thomas, and it >> makes an uncanny amount of sense. Though it doesn't have a 100% >> correlation, it does explain why just about ever-other kernel has >> exhibited this problem. >> >> I'll do a test. Right now I have 2.6.35-7 installed. I have upgraded >> to 2.6.35-8 (wouldn't boot), downgraded to 2.6.35-7 (worked), >> upgraded to 2.6.36-3 (wouldn't boot). >> >> So if this theory is correct, I should be able to start with 2.6.35-7 >> (working), upgrade to 2.6.35-8 (expect failure), then upgrade >> directly to 2.6.36-3 and (expect success) -- even though a direct >> update from 2.6.35-7 to 2.6.36-3 originally resulted in failure. >> >> If this works I'll.... > > I guess there has been something changed in the kernel26 2.6.35.8 and > above which doesn't work with your BIOS or your RAID. Either this is a > bug in kernel26 2.6.35.8 and newer or it is not a bug but a new feature > or a change which doesn't work with your probably outdated BIOS. > > I'd suggest asking kernel upstream by either filing a bug report at > kernel.org or asking on their mailing list. > > It definitely must have something to do with the kernel. Otherwise it > wouldn't work again after a kernel downgrade. > > Heiko > Heiko, I think you are correct. Because I did the test starting with 2.6.35-7 (working), upgrade to 2.6.35-8 (expect failure -- it did), then upgrade directly to 2.6.36-3 and (expect success -- it failed too). Just to be sure, I re-made the initramfs a couple of times and tried booting with them - they all failed as well. Then downgraded to 2.6.35-7 -> it works like a champ -- no matter what order it gets installed in. I'll follow up with the kernel folks. -- 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
