From: Andi Kleen <andi@firstfloor.org>
To: Tony Vroon <tony@vroon.org>
Cc: Andi Kleen <andi@firstfloor.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)
Date: Mon, 8 Sep 2008 16:04:17 +0200 [thread overview]
Message-ID: <20080908140417.GJ26079@one.firstfloor.org> (raw)
In-Reply-To: <1220876559.27320.2.camel@localhost>
On Mon, Sep 08, 2008 at 01:22:39PM +0100, Tony Vroon wrote:
> On Mon, 2008-09-08 at 12:55 +0200, Andi Kleen wrote:
> > It unfortunately turns out that mcelog logging is a tricky
> > psychological problem. How should the warning above have
> > looked like so that you would not have required "peer insight"
> > and actually just contacted your hardware vendor?
>
> Indication of the faulty part, so I know whether to contact AMD or Tyan.
> Without a clear idea of which it could quickly turn into an infinite
> redirect loop between the two.
Ok so you wanted linux-kernel to diagnose your hardware for you?
For DIMMs you can get that with --dmi if you run the latest mcelog
and if it's a memory problem.
Unfortunately the BIOS vendors in their wisdom often deliver incorrect
DMI tables, so the information is not always very useful.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-09-08 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 2:32 Tony Vroon
2008-09-07 3:16 ` Jeroen van Rijn
2008-09-07 4:22 ` Tony Vroon
2008-09-08 10:55 ` Andi Kleen
2008-09-08 11:13 ` Jeroen van Rijn
2008-09-08 12:22 ` Tony Vroon
2008-09-08 14:04 ` Andi Kleen [this message]
2008-09-08 15:52 ` Tony Vroon
2008-09-08 16:25 ` Jeroen van Rijn
2008-09-08 13:55 ` Pavel Machek
2008-09-08 14:00 ` Andi Kleen
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=20080908140417.GJ26079@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@vroon.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®