From: Chris Ball <cjb@laptop.org>
To: "Mikko C." <mikko.cal@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic on CentOS
Date: Mon, 15 Oct 2012 15:49:51 -0400 [thread overview]
Message-ID: <87fw5fy0ps.fsf@octavius.laptop.org> (raw)
In-Reply-To: <507C66E0.6070802@gmail.com> (Mikko C.'s message of "Mon, 15 Oct 2012 21:41:20 +0200")
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
next prev parent reply other threads:[~2012-10-15 19:49 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 [this message]
2012-10-15 23:10 ` Alan Cox
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=87fw5fy0ps.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--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