Bug 220269
Summary: | upgraded kernel panics | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mate Wierdl <mw-redhat> | ||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> | ||||||||
Severity: | urgent | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 5 | CC: | mw-redhat, wtogami | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
URL: | http://otthon.csi.hu/mw/kepernyo.jpeg | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2007-03-13 05:29:09 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Mate Wierdl
2006-12-19 23:55:33 UTC
Created attachment 144057 [details]
picture of screen when trying to boot
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. Can you remove "rhgb quiet" from the bootup parameters? That gives a lot more details. 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'. Created attachment 146211 [details]
the last screen of the unsuccessful boot
The last screen after I removed the "rhgb quiet" option
Created attachment 146212 [details]
movie of the whole unsuccesful boot
This is a MOV file taken with my digital camera.
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. Here is a fix to the problem: mkinitrd -v -f --preload=raid456 /boot/initrd-2.6.18-1.2257.fc5.img 2.6.18-1.2257.fc5 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. I just installed the latest kernel kernel-2.6.19-1.2288.2.4.fc5 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? |