Red Hat Bugzilla – Bug 130558
Kernel panic: Attempted to kill init!
Last modified: 2015-01-04 17:09:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7)
Description of problem:
MSI KT8N Neo based machine. Initially installed FC2 x86_64 tried to
load FC3 test1 via CD's but had problem's (I recently submitted a bug
report on this). So I updated the machine via yum and the development
channel which went fine but the machine has never booted successfully
with the FC3 kernels or Arjan's kernels. I kept a kernel of the
2.6.6-1.435.2.3 vintage around and it's the last one I've had work and
what I'm currently using. I'll attach two caps I made from the serial
console. One with noapic and acpi=off the other with them on.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Down load new kernel
Actual Results: Kernel and/or init panics
Expected Results: Machine boots
Created attachment 102956 [details]
Serial Console capture with no apic or acpi paramters
Created attachment 102957 [details]
Serial console capture with noapic and acpi=off kernel parameters
does it work with test3 or current rawhide?
It does. I wasn't able to install with FC3t3 as it was released but
on the fedora-test list I saw a message the mentioned that the
sata_nv.ko module was mistaking not included in the DVD/CD ISO initrd.
Someone pointed me to a new development boot.iso and I was able to
install using it without a problem. As far as rawhide updates are
concerned, as of the 624 kernel I don't have to do a thing when I
update a kernel. Before that I had to rebuild the initrd using the
--with=sata_nv switch to get a kernel that would boot.
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'.
I've since upgraded this machine to FC4 and it boots fine.