linux-kernel - RE: MCE reports errors that can't be verified

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 29 Oct 2018 16:59:44 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Borislav Petkov <bp@...en8.de>,
        Daniel Aberger - Profihost AG <d.aberger@...fihost.ag>
CC:     "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

> The fact that you see this, means, the error has reached the last
> notifier. So the EDAC notifier must've run too and handed the error to
> the EDAC driver.
>
> Can you send a full dmesg from that machine, privately to Tony and me is
> fine too.

Some system configuration information would be helpful. I can see from the logs
that this on a Haswell Xeon, but not which model.  The addresses of the errors
are around 448GB, how much memory does the system have? Output of
"dmidecode -t 17" would help.

There are some strange values in the snip you sent. First logged error shows a
corrected error count of 2544. Next shows just count=1 (with overflow bit set to 0).
Third has a count of 2, with overflow set.

So I'm guessing that you may have some storms of corrected errors and Linux
has switched to polling mode.

The three errors in the sample are all on the same channel (1) of the same memory
controller (0). But the addresses are different. Indicates that something serious has
happened to a DIMM on that channel.

The EDAC driver printed out those messages, but then silently failed to give any
extra detail.  Not really sure how that happened. Perhaps I'm missing some error
path where it just gives up. Can you run (as root) "lspci -xxxx" and send the output
from that. (Compress and send off list).

-Tony