From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Avuton Olrich <avuton@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic: Machine check exception
Date: Tue, 06 Dec 2005 04:13:24 -0700 [thread overview]
Message-ID: <m1wtiicwbv.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1132436886.19692.17.camel@localhost.localdomain> (Alan Cox's message of "Sat, 19 Nov 2005 21:48:06 +0000")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sad, 2005-11-19 at 12:54 -0800, Avuton Olrich wrote:
>> Is there a good way to narrow it down? I guess running a badmem
>> program would be good to start with, otherwise ...(?).
>
> A memory test may be worth doing but most machine checks indicate the
> fault is more serious than bad memory.
Although on the Opteron that is usually what it is (as memory
errors can be reported through the machine check interface)
In this case bank 4 is the appropriate bank. Although the
other bits don't look right for a memory error. I wonder
if it is that darn iommu fault again.
To decode an Opteron machine_check you can look in
the bios and kernel programmers guide. (Possibly the
architecture but I think that is too generic) to see
what all of the bits mean.
It is a pain but is faster than poking blindly in
the dark.
Eric
next prev parent reply other threads:[~2005-12-06 11:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 9:45 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 [this message]
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
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=m1wtiicwbv.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=avuton@gmail.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
all inboxes | Powered by JetHome®