On Sun, Mar 17, 2013 at 10:45 AM, Akemi Yagi wrote:
>
> Reported in the bug tracker:
>
> http://bugs.centos.org/view.php?id=6304
>
Thanks for the quick reply and will follow that discussion.
I'm still getting my head around netconsole... been a while :)
___
On Sun, Mar 17, 2013 at 7:35 AM, Kwan Lowe wrote:
> Hello all:
>
> I just updated yesterday and rebooted when I received this error:
>
> compat: exports duplicate symbol pcmcia_loop_typle (owned by kernel)
> FATAL: Error inserting dm_mod
> (/lib/modules/2.6.32.-358.2.1.el6.centos.plus.x86_64/kerne
Hello all:
I just updated yesterday and rebooted when I received this error:
compat: exports duplicate symbol pcmcia_loop_typle (owned by kernel)
FATAL: Error inserting dm_mod
(/lib/modules/2.6.32.-358.2.1.el6.centos.plus.x86_64/kernel/drivers/md/dm-mod.ko):
Invalid module format
compat: exports
-0700
>>>> From: Emmett Culley
>>>> To: centos@centos.org
>>>> Cc:
>>>> Subject: Re: [CentOS] 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,
On 03/14/2013 10:33 AM, Liam O'Toole wrote:
> On 2013-03-14, Johnny Hughes wrote:
>
> (...)
>
>> Maybe ... try this (everything done as root):
>>
>> Boot on a kernel that works and do this:
>>
>> 1. Backup you current initrd:
>>
>> cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img
>> /boot/initr
On 2013-03-14, Johnny Hughes wrote:
(...)
> Maybe ... try this (everything done as root):
>
> Boot on a kernel that works and do this:
>
> 1. Backup you current initrd:
>
> cp -a /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img
> /boot/initramfs-2.6.32-358.2.1.el6.x86_64.img.bak
OK.
>
> 2. Go to
On 03/12/2013 05:08 PM, Emmett Culley wrote:
> 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
>>> To: centos@centos.org
>
On 03/14/2013 05:17 AM, Liam O'Toole wrote:
> On 2013-03-13, Johnny Hughes wrote:
>
> (...)
>
>> On 03/13/2013 05:17 PM, Johnny Hughes wrote:
>>> On 03/13/2013 04:19 PM, Liam O'Toole wrote:
On 2013-03-13, Emmett Culley wrote:
(...)
> So let's start again.
>
> Kerne
-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: Attempt
On 2013-03-13, Johnny Hughes wrote:
(...)
> On 03/13/2013 05:17 PM, Johnny Hughes wrote:
>> On 03/13/2013 04:19 PM, Liam O'Toole wrote:
>>> On 2013-03-13, Emmett Culley wrote:
>>>
>>> (...)
>>>
So let's start again.
Kernel panic - Not syncing: Attempted to kill init!
Pid: 1,
On 2013-03-13, Johnny Hughes wrote:
(...)
> On 03/13/2013 04:19 PM, Liam O'Toole wrote:
>> On 2013-03-13, Emmett Culley wrote:
>>
>> (...)
>>
>>> 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
>>
On 03/13/2013 05:17 PM, Johnny Hughes wrote:
> On 03/13/2013 04:19 PM, Liam O'Toole wrote:
>> On 2013-03-13, Emmett Culley wrote:
>>
>> (...)
>>
>>> 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
>>
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
> On 2013-03-13, Emmett Culley wrote:
>
> (...)
>
>> 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
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
On 03/13/2013 04:19 PM, Liam O'Toole wrote:
> On 2013-03-13, Emmett Culley wrote:
>
> (...)
>
>> 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
On 2013-03-13, Emmett Culley wrote:
(...)
> 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
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
>> To: centos@centos.org
>> Cc:
>> Subject: Re: [CentOS] Kernel panic after update to
On 03/12/2013 01:48 PM, Akemi Yagi wrote:
> On Tue, Mar 12, 2013 at 1:41 PM, 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,
On Tue, Mar 12, 2013 at 1:41 PM, 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
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
20 matches
Mail list logo
