All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Vroon <tony@vroon.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)
Date: Mon, 08 Sep 2008 13:22:39 +0100	[thread overview]
Message-ID: <1220876559.27320.2.camel@localhost> (raw)
In-Reply-To: <87abeivrdf.fsf@basil.nowhere.org>

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

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.

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-09-08 12:22 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 [this message]
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=1220876559.27320.2.camel@localhost \
    --to=tony@vroon.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.