Improper Configuration or Corruption of SELinux Configuration File leads to Kernel Panic at Boot

Solution Verified - Updated -

Issue

  • A Red Hat Enterprise Linux v.6 panics during early boot, with the following message:

    Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted 2.6.32-279.el6.x86_64 #1
Call Trace
  [<ffffffff814fd11a>] ? panic+0xa0/0x168
  [<ffffffff81070db2>] ? do_exit+0862/0x870
  [<ffffffff8117ca75>] ? fput+0x25/0x30
  [<ffffffff81070c38>] ? do_group_exit+0x17/0x20
  [<ffffffff81070cc7>] ? sys_exit_group+0x17/0x20
  [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b

Environment

  • Red Hat Enterprise Linux 6
  • SELinux enabled
  • dracut

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content