Red Hat Bugzilla – Bug 249957
[mmconf] 188.8.131.52-33 hangs just before "Red Hat Nash" starts
Last modified: 2007-11-30 17:12:11 EST
Description of problem:
Kernel hangs on boot at place where "Red Hat Nash" would normally display.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. While running 2.6.21-1.3228.fc7, issue 'yum update' and allow kernel to be
2. After successful update, reboot
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-184.108.40.206-33.fc7 ro root=LABEL=/ rhgb quiet
[Linux-bzimage, setup=0x1e00, size-0x1cddc87
[Linux-initrd @ 0x1fbb7000, 0x3187c3 bytes]
Booting the kernel.
(flashing cursor -- fans go to full speed after a few seconds)
Red Hat Nash version xxxxxxx starting
Kernel 220.127.116.11-27 gets to the "Red Hat Nash" line and then produces a "Kernel
panic - not syncing: Attempted to kill init!" message.
Something about this kernel doesn't like something about my hardware. Please
let me know what additional info you need regarding same.
Some things to try:
first, update to 18.104.22.168-41, but remove the broken kernel first:
yum remove kernel-22.214.171.124-27.fc7
yum update kernel
second, try kernel options alone and in combination:
The option that makes the difference is:
None of the others have any effect.
Is this The Fix, or is this a troubleshooting step? Do you now need info
about my PCI bridge/bus/devices?
Also, does this have something to do with new functionality introduced into
2.6.22? I'm having a similar problem with kernel 2.6.22 on a VMWare guest at
work that is running FC6. Haven't filed a bugzilla for it yet.
Can you post the output of 'lspci -n' and 'lspci -v', and Motherboard/BIOS
information? Is a BIOS update available, and if so does it help?
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel? If so, could you attach
the output Chuck requested so that the issue can be investigated further.
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
(In reply to comment #4)
> If the problem no longer exists then please close this bug or I'll do so in a
> few days if there is no additional information lodged.
Please don't close any bugs marked [mmconf] or [msi] -- I'm collecting these
since they can all be fixed by adding quirks for this behavior.
Okay Chuck, added this to the wiki page as well.
Sorry for the lack of info. I went on vacation and then promptly forgot that
I had work to do on this bug. I'll get to it this weekend.
I'm embarrassed to say that I must close this bug because I can't get you the
info you require.
I run a dual-boot Fedora/SuSE system here and have for years. But the latest
SuSE (10.3) has trashed my grub in some way that causes kernel panics when I
try to boot into Fedora.
All of my troubleshooting steps have failed. So I'm going to admit defeat at
the hands of The Gecko (for now), and won't keep this bug hanging any longer.