Bug 175115 - Kernel panic on fresh install
Kernel panic on fresh install
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2005-12-06 13:09 EST by Orion Poplawski
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-06 17:51:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2005-12-06 13:09:18 EST
Description of problem:

After install of today's rawhide:

Unable to access resume device (LABEL=SWAP-hda5)
Creating root device.
created path for LABEL=/: 3/3
Mounting root filesystem.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Settting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
Synaptics Touchpad, model: 1, fw: 6.2, id: 0x23a0b1, caps: 0xa04713/0x200000
input: SynPS/2 Synaptics TouchPad as /class/input/input1
Kernel panic - not syncing: Attempted to kill init!

Call Trace: {panic+133}        {do_page_fault+1204}
            {__fput+340}       {_spin_unlock_irq+9}
            {__down_read+50}   {_spin_lock_irqsave+9}
            {__up_read+19}     {do_exit+168}
            {sys_exit_group+0} {system_call+126}

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

How reproducible:
Comment 1 Dave Jones 2005-12-06 17:04:32 EST
does it boot if you boot with selinux=0 ?
Comment 2 Orion Poplawski 2005-12-06 17:12:58 EST
Comment 3 Dave Jones 2005-12-06 17:51:56 EST
ok, thats an selinux policy bug that should be fixed now.

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