Description of problem:
We yum updated recently on a Dell Optiplex 320 running Fedora Core 6, and it no
longer boots. It gets stuck during the boot process, and here are the last few
lines before it stops:
Creating initial device nodes
Setting up hotplug.
Once it reaches that point, it just sits there.
In order to get a fully-functioning fc6 installation on the Optiplex 320, we had
to use the "pci=nomsi" boot option and lilo as the boot loader. But it worked
with the original 2.6.18-1.2798.fc6 kernel, as well as all kernel updates
through 2.6.20-1.2962.fc6, which is what one of our Optiplex 320's is running.
It has only been with this latest kernel release that we've had a problem
booting these machines.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. build Dell Optiplex 320 with fc6 (use boot option pci=nomsi).
2. install lilo; include boot option pci=nomsi in lilo.conf file.
3. run lilo -v, reboot and verify that the workstation boots.
4. yum update, which installs kernel 220.127.116.11-42.fc6.
5. run lilo -v.
6. reboot and select latest kernel.
workstation hangs during boot at "Setting up hotplug."
we expect the workstation to boot.
Seems to be specific to the Dell Optiplex 320, as far as in our shop. We've
several different i386 platforms that yum updated / rebooted just fine with the
latest fc6 kernel.
Does "noapic" make it boot?
Also, is it really dead? Some machines can take a long time to start hotplug.
Does pressing capslock make the light go on and off when it gets stuck?
adding "noapic" option does not make it boot.
yes, it really is dead. i've let it sit for a long time (> 30 minutes), and no
on/off lights from pressing capslock.
thank you, jonathan
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.