From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Mikko C." <mikko.cal@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic on CentOS
Date: Tue, 16 Oct 2012 00:10:07 +0100 [thread overview]
Message-ID: <20121016001007.35aa5bbb@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <507C66E0.6070802@gmail.com>
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
next prev parent reply other threads:[~2012-10-15 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2012-10-16 9:50 ` Akemi Yagi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121016001007.35aa5bbb@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.cal@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox