After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 Plus a call trace I couldn't see
Luckily I was able to boot from the previous kernel and get my system back up. After booting to the previous kernel I removed the "358" kernel and all of it's related module and devel packages using yum remove, then did yum update again, as I could only guess that the install somehow didn't complete. But it still fails to boot.
Now the kernel panic has happened to a 6.3 VM guest I upgraded, now it isn't just the host hardware that is a problem.
Has anyone else seen this?
Any ideas where to start troubleshooting?
Emmett
On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley emmett@webengineer.com wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1
At the time of this writing, CentOS kernel 2.6.32-358.2.1.el6 is not out yet. Where did you get this one from ??? Did you build it yourself?
Akemi
On 03/12/2013 01:48 PM, Akemi Yagi wrote:
On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley emmett@webengineer.com wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1
At the time of this writing, CentOS kernel 2.6.32-358.2.1.el6 is not out yet. Where did you get this one from ??? Did you build it yourself?
Akemi
I did yum update --enablerepo=epel. I just checked and it appears that kernel was from the updates repo:
[~]# yum list kernel Installed Packages kernel.x86_64 2.6.32-279.9.1.el6 @updates kernel.x86_64 2.6.32-279.14.1.el6 @updates kernel.x86_64 2.6.32-279.19.1.el6 @updates kernel.x86_64 2.6.32-279.22.1.el6 @updates kernel.x86_64 2.6.32-358.0.1.el6 @updates
[~]# rpm -qa |grep kernel abrt-addon-kerneloops-2.0.8-15.el6.centos.x86_64 kernel-2.6.32-279.19.1.el6.x86_64 dracut-kernel-004-303.el6.noarch kernel-devel-2.6.32-279.14.1.el6.x86_64 kernel-2.6.32-279.14.1.el6.x86_64 kernel-devel-2.6.32-279.22.1.el6.x86_64 kernel-headers-2.6.32-358.0.1.el6.x86_64 kernel-firmware-2.6.32-358.0.1.el6.noarch kernel-2.6.32-358.0.1.el6.x86_64 kernel-devel-2.6.32-279.19.1.el6.x86_64 kernel-devel-2.6.32-358.0.1.el6.x86_64 kernel-2.6.32-279.9.1.el6.x86_64 libreport-plugin-kerneloops-2.0.9-15.el6.centos.x86_64 kernel-2.6.32-279.22.1.el6.x86_64 kernel-devel-2.6.32-279.9.1.el6.x86_64
This is from a VM that succeeded with the update to the "359" kernel. There are three more like that.
Emmett
On 12.03.2013 20:41, Emmett Culley wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 Plus a call trace I couldn't see
Is selinux on? If you boot the new kernel with selinux=0 does the panic happen? I had this happen to me recently.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/13/2013 05:52 PM, Nux! wrote:
On 12.03.2013 20:41, Emmett Culley wrote:
After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to update the host as well. And it failed to boot.
Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 Plus a call trace I couldn't see
Is selinux on? If you boot the new kernel with selinux=0 does the panic happen? I had this happen to me recently.
You can leave SELinux on in permissive mode using enforcing=0.
-
Akemi Yagi -
Daniel J Walsh -
Emmett Culley -
Nux!