linux-kernel - Re: Request for MCE decode (AMD Barcelona, fam 10h)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080908140417.GJ26079@one.firstfloor.org>
Date:	Mon, 8 Sep 2008 16:04:17 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Tony Vroon <tony@...on.org>
Cc:	Andi Kleen <andi@...stfloor.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)

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@...ux.intel.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/