From: "Giangiacomo Mariotti" <gg.mariotti@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [HW PROBLEM] Intel I7 MCE. Erratum or not?
Date: Sat, 6 Dec 2008 22:43:24 +0100 [thread overview]
Message-ID: <12bfabe40812061343j400f55d8r43571c8bd514adde@mail.gmail.com> (raw)
In-Reply-To: <493AE770.5030507@shaw.ca>
On Sat, Dec 6, 2008 at 9:58 PM, Robert Hancock <hancockr@shaw.ca> wrote:
> Giangiacomo Mariotti wrote:
>>
>> Hi everyone,
>> Mcelog just logged on my new Intel I7 920 (on Linux 2.6.27.8) this :
>> MCE 0
>> HARDWARE ERROR. This is *NOT* a software problem!
>> Please contact your hardware vendor
>> CPU 0 BANK 6 MISC 202d ADDR ffeef740
>> MCG status:
>> MCi status:
>> Error overflow
>> Uncorrected error
>> MCi_MISC register valid
>> MCi_ADDR register valid
>> Processor context corrupt
>> MCA: Generic CACHE Level-2 Data-Write Error
>> STATUS ee0000000100014a MCGSTATUS 0
>>
>> I'm reporting this here, because I found in the Intel I7 Technical
>> Specification November 2008 update that something which seems very
>> similar is in fact an erratum. So my question is : Is there any way
>> for me to verify that my problem is due to one of those errata,instead
>> of a broken hardware(if we don't want to consider all those errata as
>> broken hardware)? I'm also reporting this because I thought it may be
>> useful to signal that(if actually due to those errata) these problems
>> actually occur, so it may be useful to find workarounds in the kernel
>> to not scare to death poor Linux users!
>
> Which erratum are you talking about? I don't see one in that document that
> would match this case..
>
Well, the first one seems very similar, even if it talks about a dtlb
error instead of cache error. But sure,being similar doesn't mean too
much. Number 52 seems similar too. I guess I should just give up and
admit that my hardware is broken!
next prev parent reply other threads:[~2008-12-06 21:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:21 Giangiacomo Mariotti
2008-12-06 20:58 ` Robert Hancock
2008-12-06 21:43 ` Giangiacomo Mariotti [this message]
2008-12-06 21:47 ` Robert Hancock
2008-12-06 22:16 ` Giangiacomo Mariotti
2008-12-07 3:25 ` Robert Hancock
2008-12-07 3:42 ` Giangiacomo Mariotti
2008-12-07 21:55 ` Giangiacomo Mariotti
2008-12-07 22:13 ` Arjan van de Ven
2008-12-07 23:21 ` Giangiacomo Mariotti
2008-12-08 6:48 ` Giangiacomo Mariotti
2008-12-08 7:42 ` Hidetoshi Seto
2008-12-08 8:04 ` Giangiacomo Mariotti
2008-12-08 9:36 ` Hidetoshi Seto
2008-12-08 9:56 ` Andi Kleen
2008-12-08 10:02 ` Eric Dumazet
2008-12-08 10:18 ` Andi Kleen
2008-12-08 10:26 ` Hidetoshi Seto
2008-12-08 10:53 ` Giangiacomo Mariotti
2008-12-08 11:10 ` Hidetoshi Seto
2008-12-08 11:16 ` Giangiacomo Mariotti
2008-12-08 12:04 ` Andi Kleen
2008-12-08 12:37 ` Giangiacomo Mariotti
2008-12-09 5:54 ` Giangiacomo Mariotti
2008-12-09 11:31 ` Andi Kleen
2008-12-09 11:57 ` Giangiacomo Mariotti
2008-12-15 20:59 ` Giangiacomo Mariotti
[not found] ` <alpine.DEB.1.10.0812081314010.18782@uplift.swm.pp.se>
[not found] ` <493D296B.1080205@linux.intel.com>
[not found] ` <alpine.DEB.1.10.0812081724080.18782@uplift.swm.pp.se>
[not found] ` <493D6FB4.9090909@linux.intel.com>
[not found] ` <alpine.DEB.1.10.0812082145410.18782@uplift.swm.pp.se>
[not found] ` <12bfabe40812082146r3ea000em7a8f725101a50bd5@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0812090737410.18782@uplift.swm.pp.se>
2008-12-09 7:37 ` OFFLIST " Giangiacomo Mariotti
[not found] ` <12bfabe40812082319x4ed6c9m5b744e51cdd3d838@mail.gmail.com>
[not found] ` <alpine.DEB.1.10.0812090857590.18782@uplift.swm.pp.se>
2008-12-09 8:30 ` Giangiacomo Mariotti
2008-12-09 8:34 ` Giangiacomo Mariotti
2008-12-08 10:26 ` Giangiacomo Mariotti
2008-12-08 10:57 ` Hidetoshi Seto
2008-12-08 11:14 ` Giangiacomo Mariotti
2008-12-06 22:37 ` Giangiacomo Mariotti
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=12bfabe40812061343j400f55d8r43571c8bd514adde@mail.gmail.com \
--to=gg.mariotti@gmail.com \
--cc=hancockr@shaw.ca \
--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 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®