Bug 220269 - upgraded kernel panics
Summary: upgraded kernel panics
Status: CLOSED DUPLICATE of bug 211030
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL: http://otthon.csi.hu/mw/kepernyo.jpeg
Depends On:
TreeView+ depends on / blocked
Reported: 2006-12-19 23:55 UTC by Mate Wierdl
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2007-03-13 05:29:09 UTC

Attachments (Terms of Use)
picture of screen when trying to boot (1.58 MB, image/jpeg)
2006-12-19 23:55 UTC, Mate Wierdl
no flags Details
the last screen of the unsuccessful boot (1.58 MB, image/jpeg)
2007-01-22 19:25 UTC, Mate Wierdl
no flags Details
movie of the whole unsuccesful boot (16.17 MB, video/quicktime)
2007-01-22 19:36 UTC, Mate Wierdl
no flags Details

Description Mate Wierdl 2006-12-19 23:55:33 UTC
Description of problem:

Eversince I upgraded the kernel on my system after 2.6.17-1.2187_FC5, the system
cannot boot with the new kernel.  I am attaching the photo I took of my screen
after trying to reboot with the newest kernel, 2.6.18-1.2257.fc5.  It is also at


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. make sure grub will boot kernel-2.6.18-1.2257.fc5
2. reboot
Actual results:

Kernel panics, and so the computer cannot boot.

Expected results:

Proper reboot.

Additional info:

The system is an AMD x86_64.  The hardware has not changed in more than a year.
The output of lshal is at


I have a similar system at home, and there there is no problem running the newer
kernels.  The output of lshal for my homebox is at 


As you see, on the homebox I am running kernel 2.6.18-1.2239.fc5 which is not 
yet the latest, but my office computer panicked with this 2.6.18-1.2239.fc5

Comment 1 Mate Wierdl 2006-12-19 23:55:36 UTC
Created attachment 144057 [details]
picture of screen when trying to boot

Comment 2 Mate Wierdl 2007-01-20 11:55:15 UTC
It has been a month since I posted this severe problem, and I do not see any
reaction.  I am just sending this in case people at RH/FC just forgot about it.

Comment 3 Konrad Rzeszutek 2007-01-22 17:33:34 UTC
Can you remove "rhgb quiet" from the bootup parameters? That gives a lot more

To do that, hit 'space' when GRUB shows up, hit 'e' on the kernel, scroll down
to kernel .. line, and hit 'e' again. Remove the rhgb and quite. Hit Enter and
then 'b'.

Comment 4 Mate Wierdl 2007-01-22 19:25:38 UTC
Created attachment 146211 [details]
the last screen of the unsuccessful boot

The last screen after I removed the "rhgb quiet" option

Comment 5 Mate Wierdl 2007-01-22 19:36:19 UTC
Created attachment 146212 [details]
movie of the whole unsuccesful boot

This is a MOV file taken with my digital camera.

Comment 6 Mate Wierdl 2007-01-22 19:38:41 UTC
Thx for looking into this.  If there is a better way to capture the bootscreen,
let me know.  Uploading a 16M MOV file does not look very efficient.

Comment 7 Mate Wierdl 2007-01-30 06:21:40 UTC
Here is a fix to the problem:

mkinitrd -v -f --preload=raid456 /boot/initrd-2.6.18-1.2257.fc5.img

The change I noticed after kernel-2.6.17-1.2187_FC5 is that the raid5.ko module
did not exist anymore, but only the raid456.ko module.  Since my root partition
is on a raid5 array, the bug bit me.  

Of course, I do not want to recompile initrd after every kernel upgrade, so
please either use the --preload=raid456 option at RH or let me know of another
hopefully permanent fix.

Comment 8 Mate Wierdl 2007-03-13 05:22:32 UTC
I just installed the latest kernel


and the bug is still there.  So this thing does not bite anybody else with raid5?

How are the kernels for FC6? 

I do not dare to upgrade to FC6 because of the bug.  Will I be able to boot into
runlevel 1, and run the initrd fix? 

Comment 9 Mate Wierdl 2007-03-13 05:29:09 UTC

*** This bug has been marked as a duplicate of 211030 ***

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