[lkml]   [2008]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Request for MCE decode (AMD Barcelona, fam 10h)
On Mon, Sep 8, 2008 at 12:55 PM, Andi Kleen <> wrote:
> Tony Vroon <> 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?

I suppose mcelog might be extended to point at possible tools to get a
second opinion, in case the admin would like to to be entirely
certain. In their position I can understand them when their vendor
asks them if it's the hardware and what tests they've run to rule out

Think for example a machine check that might point to faulty RAM, it
might direct the admin to run memcheck if mcelog alone isn't
compelling enough.

> Thank you.
> -Andi (who wonders if <blink> tags in syslog would be useful
> to solve this)

Yikes, ixnay to the <blinkay>. Next people will ask for flash support
to get all-singing and -dancing error messages.

-- Jeroen.

 \ /
  Last update: 2008-09-08 13:17    [W:0.066 / U:3.672 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site