From: "Jeroen van Rijn" <jvrnix@gmail.com>
To: "Tony Vroon" <tony@vroon.org>
Cc: "Andi Kleen" <andi@firstfloor.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Request for MCE decode (AMD Barcelona, fam 10h)
Date: Mon, 8 Sep 2008 18:25:39 +0200 [thread overview]
Message-ID: <8ee0b8e80809080925h47470253hc124ea54d239c931@mail.gmail.com> (raw)
In-Reply-To: <1220889138.27320.53.camel@localhost>
On Mon, Sep 8, 2008 at 5:52 PM, Tony Vroon <tony@vroon.org> wrote:
> On Mon, 2008-09-08 at 16:04 +0200, Andi Kleen wrote:
>> Ok so you wanted linux-kernel to diagnose your hardware for you?
>
> I was hoping for some help in narrowing it down, yes. Jeroen's reply was
> very helpful, and more among the line of what I was expecting. I have
> contacted all vendors involved now, and it looks like the system RAM is
> not fully compatible with the mainboard.
I'm happy to see you've got it narrowed down enough.
> With regard to the message, I would suggest an alternate wording like
> such:
>
> A hardware component in your system is failing.
> Please contact your hardware vendor(s).
> If unsure, contact your CPU vendor first.
Or this:
"A hardware component in your system is failing.
[insert specific bit if MCE is certain enough about what part]
If you can, try to narrow it down by placing it in another mainboard
(assuming you have one available), or run [memcheck, another tool].
Then contact the hardware vendor(s) in question, if uncertain, try
your CPU vendor first."
> Regards,
> Tony V.
Jeroen.
next prev parent reply other threads:[~2008-09-08 16:25 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
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 [this message]
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=8ee0b8e80809080925h47470253hc124ea54d239c931@mail.gmail.com \
--to=jvrnix@gmail.com \
--cc=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 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®