mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeroen van Rijn" <jvrnix@gmail.com>
To: "Tony Vroon" <tony@vroon.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)
Date: Sun, 7 Sep 2008 05:16:00 +0200	[thread overview]
Message-ID: <8ee0b8e80809062016r12388b59nea95f820079c39f8@mail.gmail.com> (raw)
In-Reply-To: <1220754742.8530.12.camel@localhost>

On Sun, Sep 7, 2008 at 4:32 AM, Tony Vroon <tony@vroon.org> wrote:
> On a Tyan-based system with intermittent but persistent instability, I
> have finally received a message that something might actually be wrong
> in hardware. Could you decode:
>
> MCE 0
> HARDWARE ERROR. This is *NOT* a software problem!
> Please contact your hardware vendor
> CPU 0 BANK 4 MISC c000000001000000
> STATUS fa00002000020c0f MCGSTATUS 0
> MCE 1
> HARDWARE ERROR. This is *NOT* a software problem!
> Please contact your hardware vendor
> CPU 4 BANK 4 MISC c000000001000000
> STATUS fa00000000070f0f MCGSTATUS 0

Hi Tony,

Not easily, and it's too late to parse
arch/x86/kernel/cpu/mcheck/mce_64.c and find out what it means before
I nod off. Still, before I sign off, have you tried running "mcelog
--ascii"? It needs to be run on the machine the check occured on. It
might give you something to go on before the cavalry arrives.

Best regards,
  Jeroen.

  reply	other threads:[~2008-09-07  3:16 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 [this message]
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
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=8ee0b8e80809062016r12388b59nea95f820079c39f8@mail.gmail.com \
    --to=jvrnix@gmail.com \
    --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®