[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5345A54D.2050808@akamai.com>
Date: Wed, 09 Apr 2014 15:53:49 -0400
From: Jason Baron <jbaron@...mai.com>
To: Borislav Petkov <bp@...en8.de>
CC: "Luck, Tony" <tony.luck@...el.com>,
Aristeu Rozanski <aris@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"mingo@...nel.org" <mingo@...nel.org>,
"dougthompson@...ssion.com" <dougthompson@...ssion.com>,
"m.chehab@...sung.com" <m.chehab@...sung.com>,
"mitake@....info.waseda.ac.jp" <mitake@....info.waseda.ac.jp>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] ie31200_edac: Add driver
On 04/09/2014 03:14 PM, Borislav Petkov wrote:
> On Wed, Apr 09, 2014 at 02:57:19PM -0400, Jason Baron wrote:
>> Right, so maybe the fact that its a desktop chipset means that it
>> behaves differently and doesn't raise MCEs on memory errors. We have a
>> bunch of these processors and we haven't yet seen an MCE raised on a
>> memory error.
>
> This can't be - an uncorrectable error will have to generate a machine
> check exception if consumed - there's no other option.
>
> Can you do
>
> rdmsr 0x179
> rdmsr 0x17b
>
> and paste the results here?
>
Unfortunately, the box reporting the ue errors just went into transit (so
that I can better examine this issue), so I will probably not be able to
run this experiment on that specific box until next week.
However, I was able to run it on a very similar box (same pci id for the
mch), and I get:
# ./rdmsr 0x179
c09
# ./rdmsr 0x17b
rdmsr: CPU 0 cannot read MSR 0x0000017b
Thanks,
-Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists