Red Hat Bugzilla – Bug 170487
Bad: kernel panic on boot (kernel-2.6.9-22.EL)
Last modified: 2007-11-30 17:07:21 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7
Description of problem:
The problem appeared on a kickstart instalation for GLS server1 configuration on a Asus L4000 laptop.
After `up2date -u` new kernel packages were installed:
While booting from the new 2.6.9-22 kernel, it hangs with the following message:
Kernel panic - not syncing: Fatal exception
With the old kernel 2.6.9-5 evething works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the package kernel-2.6.9-22.EL
2. Boot the system from the new kernel
3. Kernel panic
Actual Results: It is unable to boot the system from the kernel-2.6.9-22.EL or kernel-smp-2.6.9-22.EL
ok. to help narrow this down could you try the U1 kernel? 2.6.9-11.EL? Also, any
other bootup messages would be helpful. thanks.
I had similar problem on network startup and when loading modules
for diva server card. I am quite positive that it has something to do with
When loading capifs module with enforcing selinux kernel panics. When in
permissive mode I am able to load the module in question.
The same problem occurs on kernel-2.6.9-11.EL but with all other updates
in place (I've just updated to U2).
As far as I remember kernel panic info pointed to some filesystem operations.
ok. thanks. It would certainly be helpful if you could capture the panic. thanks.
It doesn't work with the U1 kernel 2.6.9-11.EL either. You can see the screens
with bootup messages at:
I also uploaded there the /etc/sysconfig/hwconf file which might be helpful.
I believe this is the capifs bug, which has a patch upstream and also in Fedora.
The patch needs to go into RHEL, but it can also be worked around in policy.
I will add policy to work around this bug in selinux-policy-targeted-1.17.30-2.117
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.