From: Jason Baron <jbaron@akamai.com>
To: "Luck, Tony" <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: "hpa@zytor.com" <hpa@zytor.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"dougthompson@xmission.com" <dougthompson@xmission.com>,
"m.chehab@samsung.com" <m.chehab@samsung.com>,
"mitake@dcl.info.waseda.ac.jp" <mitake@dcl.info.waseda.ac.jp>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ie31200_edac: Add driver
Date: Tue, 08 Apr 2014 23:03:08 -0400 [thread overview]
Message-ID: <5344B86C.8000905@akamai.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31E21864@ORSMSX106.amr.corp.intel.com>
On 04/08/2014 06:34 PM, Luck, Tony wrote:
>>> Btw, this driver is polling, AFAICT. Doesn't e3-12xx support the CMCI
>>> interrupt which you can feed into this driver directly and thus not need
>>> the polling at all?
>> On the system with the ce and ue events that I'm testing on, I don't see
>> 'MCE' nudge above 0, in /proc/interrupts. So I think that implies that
>> we are not getting any CMCI there?
> CMCI will bump up the "THR" (Threshold) entries in /proc/interrupts.
Ok, so on the system with ue and ce events (as reported by driver
and confirmed with a memory scanner), "THR" is 0 across
all cpus, and I see no machine checks in the logs...
>> So if possible maybe we can confirm with Intel whether we expect an MCE
>> for memory errors...
> MCG_CAP bit 10 tells you whether a given processor implements CMCI.
> If that is set - then MCi_CTL2 bit 30 indicates whether a given bank
> supports it (Linux tries to set this bit, if it sticks, then it knows that CMCI
> is supported - Linux also assigns ownership of the bank to the first cpu
> to successfully set it (since a bank may be shared by multiple threads/cores
> on a package).
>
> Consumed uncorrectable errors should generate a machine check. Which
> on the E3-12xx series will be a fatal machine check: MCi_STATUS.PCC=1
>
> -Tony
>
Hmmm...as I said, I'm not getting any machine checks with ue errors. I've
got a fairly old kernel on the system atm, I will try loading a newer kernel,
to see if that makes any difference...
Thanks,
-Jason
next prev parent reply other threads:[~2014-04-09 3:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 21:13 [PATCH 0/3] Add new ie31200_edac driver Jason Baron
2014-04-04 21:13 ` [PATCH 1/3] readq/writeq: Add explicit lo_hi_[read|write]_q and hi_lo_[read|write]_q Jason Baron
2014-04-04 21:13 ` [PATCH 2/3] x38_edac: make use of lo_hi_readq() Jason Baron
2014-04-04 21:14 ` [PATCH 3/3] ie31200_edac: Add driver Jason Baron
2014-04-08 9:09 ` Borislav Petkov
2014-04-08 22:16 ` Jason Baron
2014-04-08 22:34 ` Luck, Tony
2014-04-09 3:03 ` Jason Baron [this message]
2014-04-09 11:11 ` Borislav Petkov
2014-04-09 11:13 ` Borislav Petkov
2014-04-09 11:35 ` Borislav Petkov
2014-04-09 13:34 ` Aristeu Rozanski
2014-04-09 17:17 ` Luck, Tony
2014-04-09 17:36 ` Borislav Petkov
2014-04-09 18:57 ` Jason Baron
2014-04-09 19:14 ` Borislav Petkov
2014-04-09 19:53 ` Jason Baron
2014-04-09 20:16 ` Borislav Petkov
2014-04-09 21:33 ` Luck, Tony
2014-04-09 22:15 ` Jason Baron
2014-04-09 22:44 ` Luck, Tony
2014-04-10 1:52 ` Jason Baron
2014-04-10 9:30 ` Borislav Petkov
2014-06-11 21:54 ` Jason Baron
2014-04-09 18:42 ` Jason Baron
2014-04-07 20:00 ` [PATCH 0/3] Add new ie31200_edac driver Borislav Petkov
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=5344B86C.8000905@akamai.com \
--to=jbaron@akamai.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mingo@kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=tony.luck@intel.com \
/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