* Kernel panic on CentOS
@ 2012-10-15 19:41 Mikko C.
2012-10-15 19:49 ` Chris Ball
2012-10-15 23:10 ` Alan Cox
0 siblings, 2 replies; 4+ messages in thread
From: Mikko C. @ 2012-10-15 19:41 UTC (permalink / raw)
To: linux-kernel
Hi,
we keep getting kernel panics on our CentOS 6.3 server, running about 40
KVM virtual machines.
Here's the screenshot of the trace: http://i.imgur.com/yaRyF.png
# uname -a
Linux srv010 2.6.32-71.el6.x86_64 #1 SMP Fri May 20 03:51:51 BST 2011
x86_64 x86_64 x86_64 GNU/Linux
CPU is Intel i7-2600K with 32GB DDR3 ram.
If there's any more info we can provide, please let me know.
Thanks
Mikko
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel panic on CentOS
2012-10-15 19:41 Kernel panic on CentOS Mikko C.
@ 2012-10-15 19:49 ` Chris Ball
2012-10-15 23:10 ` Alan Cox
1 sibling, 0 replies; 4+ messages in thread
From: Chris Ball @ 2012-10-15 19:49 UTC (permalink / raw)
To: Mikko C.; +Cc: linux-kernel
Hi,
On Mon, Oct 15 2012, Mikko C. wrote:
> we keep getting kernel panics on our CentOS 6.3 server, running about
> 40 KVM virtual machines.
>
> Here's the screenshot of the trace: http://i.imgur.com/yaRyF.png
The presence of machine_check() suggests that you have a hardware
problem that the kernel doesn't know how to recover from.
(Although you only sent part of the trace.)
http://en.wikipedia.org/wiki/Machine_Check_Exception
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel panic on CentOS
2012-10-15 19:41 Kernel panic on CentOS Mikko C.
2012-10-15 19:49 ` Chris Ball
@ 2012-10-15 23:10 ` Alan Cox
2012-10-16 9:50 ` Akemi Yagi
1 sibling, 1 reply; 4+ messages in thread
From: Alan Cox @ 2012-10-15 23:10 UTC (permalink / raw)
To: Mikko C.; +Cc: linux-kernel
On Mon, 15 Oct 2012 21:41:20 +0200
"Mikko C." <mikko.cal@gmail.com> wrote:
> Hi,
> we keep getting kernel panics on our CentOS 6.3 server, running about 40
> KVM virtual machines.
>
> Here's the screenshot of the trace: http://i.imgur.com/yaRyF.png
>
> # uname -a
> Linux srv010 2.6.32-71.el6.x86_64 #1 SMP Fri May 20 03:51:51 BST 2011
> x86_64 x86_64 x86_64 GNU/Linux
>
> CPU is Intel i7-2600K with 32GB DDR3 ram.
>
> If there's any more info we can provide, please let me know.
You are in the wrong place - the Red Hat enterprise kernels deviate a lot
from upstream and are very old. Really you need to go back to the Centos
community with it.
Alan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel panic on CentOS
2012-10-15 23:10 ` Alan Cox
@ 2012-10-16 9:50 ` Akemi Yagi
0 siblings, 0 replies; 4+ messages in thread
From: Akemi Yagi @ 2012-10-16 9:50 UTC (permalink / raw)
To: linux-kernel
On Tue, 16 Oct 2012 00:10:07 +0100, Alan Cox wrote:
> On Mon, 15 Oct 2012 21:41:20 +0200 "Mikko C." <mikko.cal@gmail.com>
> wrote:
>
>> Hi,
>> we keep getting kernel panics on our CentOS 6.3 server, running about
>> 40 KVM virtual machines.
>>
>> Here's the screenshot of the trace: http://i.imgur.com/yaRyF.png
>>
>> # uname -a Linux srv010 2.6.32-71.el6.x86_64 #1 SMP Fri May 20 03:51:51
>> BST 2011 x86_64 x86_64 x86_64 GNU/Linux
> You are in the wrong place - the Red Hat enterprise kernels deviate a
> lot from upstream and are very old. Really you need to go back to the
> Centos community with it.
>
> Alan
This is more like general info/tip: anyone wishing to test the latest
mainline/stable kernels from kernel.org on RHEL systems can do so by
installing kernel-ml [1] from the ELRepo Project. As of today, 3.6.2 and
3.0.46 are available for RHEL-6.
Akemi
[1] http://elrepo.org/tiki/kernel-ml
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-10-16 9:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-15 19:41 Kernel panic on CentOS Mikko C.
2012-10-15 19:49 ` Chris Ball
2012-10-15 23:10 ` Alan Cox
2012-10-16 9:50 ` Akemi Yagi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox