Red Hat Bugzilla – Bug 476395
boot hang at starting udev fc9
Last modified: 2009-07-14 11:53:29 EDT
Description of problem:
I was running fc9 22.214.171.124-79 on Toshiba laptop with no problems, but after fc9 126.96.36.199-37 update, machine would not complete boot up, last message on screen is starting udev, but it never gets the OK message. A couple days later, update fc9 188.8.131.52-41 was received, with same problem. I have seen threads that have a similar problem, and have found workarounds for the startup, but none have worked on my machine. I would like to know what to look for to try to diagnose the problem. I can still boot up on 26.26.6-79, but I have not found any logs or messages that indicate the failed boot. I removed the two faulty kernels, and update took over again and put fc9 184.108.40.206-41 back. I allowed it, to see if reinstalling the kernel would maybe correct the "mismatch", but still 220.127.116.11-41 hangs at starting udev. I have searched all the logs that I know of, but don't know where to capture the docs to send. I have recently received kernel 18.104.22.168-53 with the same results.
Version-Release number of selected component (if applicable):
22.214.171.124-79 - working
126.96.36.199-37 - hang
188.8.131.52-41 - hang
184.108.40.206-53 - hang
Steps to Reproduce:
1. accept kernel update
2. boot to new kernel
system hangs after displaying starting udev message, never completing.
OK message from udev, boot process completing
Let me know what info that I can gather
I have received kernel 220.127.116.11.73, which also hangs. Is there a way to set a verbose flag or log to see where it is stopping?? I would like to get this resolved, as I do like to keep current.
Again, what can I capture to help determine what is amiss this the udev, or is there a better place to get info on the process?
I can confirm this on an HP Pavilion DV6809WM with kernel 18.104.22.168.73. It only happens when I have the laptop unplugged. If I plug it in after it hangs at any point it will finish booting. Also, when resuming after suspend all I get is a blank screen. These were not an issue with 22.214.171.124-79 but have been for each kernel since then.
Some new info from my end. If I boot kernel 126.96.36.199-73.fc9.i686 acpi=off pci=noacpi, it will boot just fine without the power cable plugged in. Also, I am in the process of comparing the /var/log/messages differences between booting 188.8.131.52-73 and 184.108.40.206-79.
try to start with "modprobedebug" added to the kernel command line.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.