Red Hat Bugzilla – Bug 433896
2.6.25 kernel won't boot
Last modified: 2008-09-14 20:47:53 EDT
On my hardware, 2.6.24 rawhide kernel works perfectly. 2.6.25 kernel hangs during interactive startup: usually at udev, but occasionally makes it to setting hostname or next one. I've tried noacpi, noapic, nolapic, and nohz=off without improvement. Hardware in brief is Core2Duo ULV U7500, Intel X3100 video, 1 GB ram, ICH8 HDA audio and modem, IWL4965 BGN wireless, sky2 gigabit ethernet, Bluetooth, aes2501 fingerprint reader. More info to follow.
Created attachment 295647 [details] dmesg output
Created attachment 295648 [details] dmidecode output
Created attachment 295649 [details] lsmod output (2.6.24)
Created attachment 295650 [details] lspci -v output
Strangely, if I wait long enough (a few minutes) I see "timeout, proceeding in background" or something like that. Then the bootsplash appears, but without text. The boot proceeds, but graphical elements only, no text. Finally, near the end of the boot, it truly hangs, without gdm having shown up yet, and the hard drive goes to sleep.
did you try a newer release? Did it work?
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.