Red Hat Bugzilla – Bug 155264
kernel panic during boot process.
Last modified: 2015-01-04 17:18:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Fedora/1.7.6-1.2.5
Description of problem:
The kernel-smp-2.6.11-1.14_FC3 gives me a kernel panic immediately at boot time, and complains about /lib/ld.so . It couldn't be found since it doesn't exist. This is repeatable until I boot up with kernel-2.6.11-1.14_FC3 just once, which is booting up just fine. After that the kernel panic does not occur with kernel-smp-2.6.11-1.14_FC3 (which explains why I don't have unfortunately more details about the error message), but instead it gives me a mounting error of the ext3fs just after it loaded the hardware modules.
Unfortunately I'm not willing to sacrifice the servers again so I'm discontinuing the experimenting (I had some VERY BAD experience with kernel-smp-2.6.10-1.760_FC3, the consequences were far more serious than reported in bugzilla). I'm seriously questioning if the smp kernels are even tested before submitted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora Core 3 with kernel-smp-2.6.11-1.14_FC3 on an equivalent system.
2. Try to boot with the smp kernel.
Actual Results: kernel panic or mounting error of ext3fs
Expected Results: The system should have booted up nice and clean, just like with kernel-smp-188.8.131.520_FC3
My system has the following configuration:
MB: TYAN Tiger K8W (s2875)
CPU: 2 x Opteron_242
HDD: 2 x 200GB (/boot as RAID1; / as RAID0; swap as RAID0)
Memory: 2 x 1GB = 2GB
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.