Bug 433896 - 2.6.25 kernel won't boot
Summary: 2.6.25 kernel won't boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-21 23:35 UTC by Austin Acton
Modified: 2008-09-15 00:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-09-15 00:47:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output (33.45 KB, application/octet-stream)
2008-02-22 16:26 UTC, Austin Acton
no flags Details
dmidecode output (9.29 KB, application/octet-stream)
2008-02-22 16:26 UTC, Austin Acton
no flags Details
lsmod output (2.6.24) (3.76 KB, application/octet-stream)
2008-02-22 16:26 UTC, Austin Acton
no flags Details
lspci -v output (10.17 KB, text/plain)
2008-02-22 16:27 UTC, Austin Acton
no flags Details

Description Austin Acton 2008-02-21 23:35:38 UTC
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.

Comment 1 Austin Acton 2008-02-22 16:26:01 UTC
Created attachment 295647 [details]
dmesg output

Comment 2 Austin Acton 2008-02-22 16:26:22 UTC
Created attachment 295648 [details]
dmidecode output

Comment 3 Austin Acton 2008-02-22 16:26:53 UTC
Created attachment 295649 [details]
lsmod output (2.6.24)

Comment 4 Austin Acton 2008-02-22 16:27:13 UTC
Created attachment 295650 [details]
lspci -v output

Comment 5 Austin Acton 2008-02-23 00:16:23 UTC
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.

Comment 6 Rahul Sundaram 2008-04-12 08:03:35 UTC
did you try a newer release? Did it work?

Comment 7 Bug Zapper 2008-05-14 05:19:39 UTC
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

Comment 8 Brennan Ashton 2008-06-08 02:45:27 UTC
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.

Comment 9 petrosyan 2008-09-15 00:47:53 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.