From: Andi Kleen <andi@firstfloor.org>
To: Tony Vroon <tony@vroon.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)
Date: Mon, 08 Sep 2008 12:55:40 +0200 [thread overview]
Message-ID: <87abeivrdf.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1220754742.8530.12.camel@localhost> (Tony Vroon's message of "Sun, 07 Sep 2008 03:32:22 +0100")
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.
> 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)
next prev parent reply other threads:[~2008-09-08 10:55 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 [this message]
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=87abeivrdf.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--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 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.