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]

Date:	Mon, 08 Sep 2008 12:55:40 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Tony Vroon <tony@...on.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)

Tony Vroon <tony@...on.org> writes:

> HARDWARE ERROR. This is *NOT* a software problem!
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Please contact your hardware vendor
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> I realize that the linux kernel may be entirely blameless in this
> situation,

It is, like mcelog told you.

> but I'd like to have some peer insight before I run after
> vendors.

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? 

Thank you.

-Andi (who wonders if <blink> tags in syslog would be useful 
to solve this)
--
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/