public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jason Baron <jbaron@akamai.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Aristeu Rozanski <aris@redhat.com>,
	"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: Wed, 9 Apr 2014 22:16:15 +0200	[thread overview]
Message-ID: <20140409201615.GS6529@pd.tnic> (raw)
In-Reply-To: <5345A54D.2050808@akamai.com>

On Wed, Apr 09, 2014 at 03:53:49PM -0400, Jason Baron wrote:
> 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

1100_0000_1001
11   7    3

Hohumm, that's interesting: 9 MCE banks, there's *no* MCG_CTL register
present (bit 8) (that's why the read below fails) so you cannot turn on
or off the error reporting banks.

bit 10 says you have CMCI so you don't need the polling, you probably
don't even need the EDAC driver at all ... unless you want to report
which DRAM channel had the error (this is probably the only additional
information your drivers gives and which the info in mcelog won't give).

Which gives the next question: what exactly is this EDAC driver going
to be used for if it reports (row, channel, syndrome) and how are you
going to use that info? I'm looking at ie31200_process_error_info().

> # ./rdmsr 0x17b
> rdmsr: CPU 0 cannot read MSR 0x0000017b

In any case, that's some strange machine. If it is a desktop MCH, I can
understand it not raising MCEs but that would be pretty nasty, still.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-04-09 20:16 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
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 [this message]
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=20140409201615.GS6529@pd.tnic \
    --to=bp@alien8.de \
    --cc=aris@redhat.com \
    --cc=dougthompson@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jbaron@akamai.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