[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181029182557.GA13320@agluck-desk>
Date: Mon, 29 Oct 2018 11:25:57 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Daniel Aberger - Profihost AG <d.aberger@...fihost.ag>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>, "x86@...nel.org" <x86@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"s.priebe@...fihost.ag" <s.priebe@...fihost.ag>,
"n.fahldieck@...fihost.ag" <n.fahldieck@...fihost.ag>,
"p.kramme@...fihost.ag" <p.kramme@...fihost.ag>
Subject: Re: MCE reports errors that can't be verified
On Mon, Oct 29, 2018 at 06:51:29PM +0100, Borislav Petkov wrote:
> On Mon, Oct 29, 2018 at 04:59:44PM +0000, Luck, Tony wrote:
> > The EDAC driver printed out those messages,
>
> I don't think so - that's __print_mce() in mce.c which dumps the three
> lines under "... events logged". Which means, that's the lowest prio,
> fallback notifier which runs when nothing else before it has done any
> logging.
Ah yes. In which case the EDAC driver wasn't loaded (or gave up
silently) to let us arrive at the end of the decode chain.
Another question. Does /proc/interrupts show a lot of CMCI (for
historical reasons this is the THR: line).
-Tony
Powered by blists - more mailing lists