On 03/12/2013 04:23 PM, lists-centos wrote:
>
>
> ------------ Original Message ------------
>> Date: Tuesday, March 12, 2013 04:05:28 PM -0700
>> From: Emmett Culley <emmett@xxxxxxxxxxxxxxx>
>> To: centos@xxxxxxxxxx
>> Cc:
>> Subject: Re: Kernel panic after update to 6.4
>>
>> On 03/12/2013 01:48 PM, Akemi Yagi wrote:
>>> On Tue, Mar 12, 2013 at 1:41 PM, Emmett Culley
>>> <emmett@xxxxxxxxxxxxxxx> 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
>>
>
> You are giving conflicting information.
>
> You indicated that the kernel that you are getting the panic on is:
>
> >> Kernel panic - Not syncing: Attempted to kill init!
> >> Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1
>
> i.e., ...358.2.1
>
> What you are showing as available from @updates and installed in the
> VM that is working is:
>
> kernel.x86_64 2.6.32-358.0.1.el6 @updates
>
> kernel-2.6.32-358.0.1.el6.x86_64
>
> i.e., ...358.0.1
>
>
> RedHat released ...358.2.1 earlier today, but I haven't seen centos
> announce its release yet, and it's not available from the centos
> repositories as of a few moments ago. So, the VM that is ok is using
> ...358.0.1, the centos released kernel. The one that is panic would
> appear to have come from elsewhere.
>
> Also note, it's the "358", not "359" kernel:
>
> > This is from a VM that succeeded with the update to the "359"
> > kernel. There are three more like that.
Yes, kernel "358". the "359" was a typo. And... the kernel panic lines were transcribed for a photo I took of the screen after the failed boot. On second look I see that the version is 2.6.32-358.0.1.el6.x86_64.
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1, comm: init not tainted: 2.6.32-358.0.1.el6.x86_64 #1
After yum upgrade --enablerepo=epel on two of five machines, one of which is the host for the three VM's that succeeded and the one that failed, just as the host.
I have a screen shot of that VM's boot failure, but I don't know the proper way to include it in a post.
I've uninstalled that kernel and ran yum upgrade again, it still fails on that kernel, on both the host and the VM. I suppose the good thing is that it happened on a VM guest that is not critical, so I don't have to experiment with the host that has four important guests running on it.
Any ideas?
Emmett
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
