From: Andi Kleen <ak@suse.de>
To: Avuton Olrich <avuton@gmail.com>
Cc: Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic: Machine check exception
Date: Tue, 6 Dec 2005 19:47:08 +0100 [thread overview]
Message-ID: <20051206184708.GV11190@wotan.suse.de> (raw)
In-Reply-To: <3aa654a40512061045h33fea2a0y1511366df2e7c166@mail.gmail.com>
On Tue, Dec 06, 2005 at 10:45:36AM -0800, Avuton Olrich wrote:
> On 06 Dec 2005 12:45:44 -0700, Andi Kleen <ak@suse.de> wrote:
> > ebiederm@xmission.com (Eric W. Biederman) writes:
> > >
> > > To decode an Opteron machine_check you can look in
> > > the bios and kernel programmers guide. (Possibly the
>
> > mcelog --ascii decodes the "final" machine checks output
> > by the 64bit kernel. The normal recoverable machine checks
> > should be decoded at runtime assuming your distribution
> > set it up right (normally into /var/log/mcelog)
>
> That also works on kernel panic?
The automatic logging doesn't work during panic, but if you
redirected the output of the kernel panic to some other machine
(using serial console etc) you can pipe that log
into it for decoding.
-Andi
next prev parent reply other threads:[~2005-12-06 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 9:45 Kernel panic: Machine check exception Avuton Olrich
2005-11-19 9:55 ` Avuton Olrich
2005-11-19 10:02 ` Arjan van de Ven
2005-11-19 10:04 ` Avuton Olrich
2005-11-19 13:24 ` Alan Cox
2005-11-19 20:54 ` Avuton Olrich
2005-11-19 21:48 ` Alan Cox
2005-11-19 22:24 ` Nix
2005-12-06 11:13 ` Eric W. Biederman
2005-12-06 13:23 ` Avuton Olrich
2005-12-06 19:45 ` Andi Kleen
2005-12-06 18:45 ` Avuton Olrich
2005-12-06 18:47 ` Andi Kleen [this message]
2005-12-08 2:46 ` Avuton Olrich
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=20051206184708.GV11190@wotan.suse.de \
--to=ak@suse.de \
--cc=avuton@gmail.com \
--cc=ebiederm@xmission.com \
--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