linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Andi Kleen <andi@firstfloor.org>, Tony Vroon <tony@vroon.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)
Date: Mon, 8 Sep 2008 16:00:27 +0200	[thread overview]
Message-ID: <20080908140027.GI26079@one.firstfloor.org> (raw)
In-Reply-To: <20080908135558.GA31784@elf.ucw.cz>

On Mon, Sep 08, 2008 at 03:55:58PM +0200, Pavel Machek wrote:
> On Mon 2008-09-08 12:55:40, Andi Kleen wrote:
> > Tony Vroon <tony@vroon.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.
> 
> Ugh, actually this is not right. AFAIK MCEs can be triggered by stuff
> like PCI aborts, which in turn can be caused by software.

PCI aborts don't normally cause machine checks, no.

-Andi
-- 
ak@linux.intel.com

      reply	other threads:[~2008-09-08 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07  2:32 Request for MCE decode (AMD Barcelona, fam 10h) 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
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 [this message]

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=20080908140027.GI26079@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).