Manufacturer: TOSHIBA Product Name: Qosmio X500 Version: PQX33U-01H01M
Sorry about the little blip up top... Must have hit enter by mistake. Anyway.... Last week I opened up a bug report at: https://bugzilla.redhat.com/show_bug.cgi?id=649181 When I boot into Kernel 2.6.35.6-48.fc14.x86_64 (Fedora's current build) I get a kernel panic unless I use the boot parameter acpi=off The details of what information that I'm able to provide are in the above mentioned bug report. Thank you for your attention on this matter
please remove the boot option "rhgb quiet" and reboot. it would be great if you take a screenshot with DC when the system hangs, and attach it here.
is it possible to boot kernels built from the upstream kernel tree rather than the fedora source tree? (you can use fedora's .config if you like) In particular, it would be good to find the latest upstream kernel that works and the earliest upstream kernel that fails. Indeed, a git bisect may tell us exactly what commit breaks this machine.
(In reply to comment #2) > please remove the boot option "rhgb quiet" and reboot. > it would be great if you take a screenshot with DC when the system hangs, and > attach it here. This would be extremely difficult as the computer crashes on boot. I did try to take a video with a camera that I had in hopes that I could split parts of boot process into stills, but the image is very very bad. Really its imposible to see anything.
I can certainly try... Its been years since I've compiled a kernel from scratch you might need to do some hand holding on that one. I would be very happy to try to do a bisect, but you will have to hand my hand on this one for sure.
Oh... I'm assuming that you would like to start with 2.6.34? Please let me know how you would like to proceed. Thanks
Please let me know if the procedure that I'm following is sound What I've decided to do is to start with 2.6.35 1) I've downloaded the source rpm from Fedora 2) Installed the source rpm 3) Modified the SPEC file to eliminate any reference to anything dealing with ACPI. 4) rebuild the kernel Same kernel panic at boot. The next step will be to eliminate any reference to any patches in the SPEC file and rebuild. If that does work, then I will start to try to find what patch has caused the kernel panic. If I continue to get the panic after that I will then start working with the 2.6.34 src rpm in the manner outlined above. Thanks for any comment you are willing to provide
Yippee!!!! I found the kernel where the problem was introduced. Created vanilla kernels for linux-2.6.35.1-4 Upto 2.6.35.3 the computer seemed to have booted up normally. With 2.6.35.4 I got a kernel panic at boot time. So..... What's the next step? Thank you so much for you assistance on this.
Well, I finally found the problem and as it turns out it wasn't a kernel problem per se.... I hope that what I'm about to report doesn't get you too annoyed with me. With your coaching and the coaching over at Fedora, I was finally able to narrow down the problem to a kmod that I used to need... That being the kmod for the omnibook drivers. It turns out that not only do I not need them anymore, but that they cause a conflict. Once I removed the omnibook drivers all was well. Thank you so much for your time, effort and coaching Sincerely