Bug 235985 - Kernel panic: not syncing: attempted to kill init
Kernel panic: not syncing: attempted to kill init
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-11 04:25 EDT by herman
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-23 16:57:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description herman 2007-04-11 04:25:41 EDT
Description of problem:
When booting, kernel panics:
message: "kernel panic: not syncing! attempted to kill init

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

Linux 2.6.20-1.3054.fc7

How reproducible:
Just reboot with the same kernel, happens all the time.

Steps to Reproduce:
1.Reboot
2.
3.
  
Actual results:
Identical

Expected results:


Additional info:
cpu this occurred on:
AMD Athlon XP 2600+ @ 1.9 GHz
Comment 1 Dave Jones 2007-04-13 14:53:49 EDT
try reinstalling the kernel rpm, but this time do setenforce 0 first.
If that works, it's a mkinitrd vs selinux-policy bug.

Someone mentioned something similar in #fedora-devel yesterday, which is why I'm
thinking this could be the reason.
Comment 2 herman 2007-04-14 12:17:56 EDT
I can't find that rpm, I'm very sorry. I'll check it out if you can give me a
mirror. It's not in 'my' repos anymore. Is it still relevant?
Running *.3062 now.
Comment 3 Dave Jones 2007-04-23 12:03:56 EDT
3062 (and later) works ? If so, this can be closed.
Comment 4 herman 2007-04-23 16:18:53 EDT
All of the later kernels work.
Comment 5 herman 2007-04-23 16:20:15 EDT
3062 and later kernels work.

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