From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: MCEs
Date: Sat, 25 Oct 2008 01:07:48 +0200 [thread overview]
Message-ID: <20081024230748.GA21365@codeblau.de> (raw)
In-Reply-To: <87r66598eq.fsf@basil.nowhere.org>
> It's some sort of hardware problem, debugging it typically
> either involves fixing the cooling or exchanging components.
Using an older kernel I get actual MCE messages that I can write down
and decode using mcelog.
It looks like the MCE handler is buggy in current kernels and will cause
a panic instead of the MCE messages (or maybe in addition to and the
panic obscures them by scrolling them out of my 80x25 screen).
Is there a howto or wiki somewhere on how to parse mcelog decoded
messages?
Felix
next prev parent reply other threads:[~2008-10-24 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 12:45 MCEs Felix von Leitner
2008-10-24 16:23 ` MCEs Tony Vroon
2008-10-24 18:04 ` MCEs Andi Kleen
2008-10-24 21:44 ` MCEs Felix von Leitner
2008-10-24 23:07 ` Felix von Leitner [this message]
2008-10-25 7:00 ` MCEs Andi Kleen
2008-10-25 10:05 ` MCEs Felix von Leitner
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=20081024230748.GA21365@codeblau.de \
--to=felix-linuxkernel@fefe.de \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
/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