Red Hat Bugzilla – Bug 187983
Receive a kernel panic after upgrade from FC2 -> FC5
Last modified: 2008-02-05 08:35:13 EST
Description of problem:
Completed the FC5 upgrade and everything appeared to work normally. After
upgrade was complete and the system was rebooted, I received a kernel panic.
Version-Release number of selected component (if applicable):
FC5 (dated March 15, 2006) retrieved March 29, 2006.
Steps to Reproduce:
1. boot system
Booting `Fedora Core (2.6.15-1.2054_FC5)'
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.14-1.2054_FC5 ro root=LABEL=/ rhgb quiet
[Linux-bzImage, setup=0x1e00, size=0x16eb71]
[Linux-initrd @ 0xbdff000, 0xe0cff bytes]
Uncompressing Linux... Ok, booting kernel.
Red Hat nash version 5.0.32 starting
kernel panic - not syncing. Attempted to kill init!
Proper system boot
SHA1SUM of the downloaded ISO images were validated.
System that was upgraded is an HP Pavilion 6638
noticed a typo, the kernel is /vmlinuz-2.6.15-1.2054_FC5
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug after installing all the
current updates, please reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.
Closing since there was an error in previous mass-close and they remained in