linux-kernel - RE: [lkp] [EDAC, sb_edac] 2c1ea4c700: kmsg.EDAC_sbridge:Failed_to_register_device_with

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] [day] [month] [year] [list]

Date:	Tue, 24 May 2016 17:12:56 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Ye, Xiaolong" <xiaolong.ye@...el.com>
CC:	Borislav Petkov <bp@...e.de>, Borislav Petkov <bp@...en8.de>,
	LKML <linux-kernel@...r.kernel.org>, "lkp@...org" <lkp@...org>
Subject: RE: [lkp] [EDAC, sb_edac] 2c1ea4c700:
 kmsg.EDAC_sbridge:Failed_to_register_device_with_error

> [   55.677523] EDAC sbridge: ECC is disabled. Aborting

Works on my HSW-EX. Maybe it depends on memory configuration or some BIOS settings?

The EDAC driver is looking at the MCMTR register to determine whether ECC is enabled (and this
change in the code shouldn't really affect that).

What does:

# setpci -d 8086:2fa8 0x7c.L

say? It should print a hex number for each socket. The 0x4 bit is the ECC enable bit. On my machine it
says:

00017d0d

for all four sockets ... so ECC is enabled every place we look.

The kmsg file is a bit confusing too.  There are 32 "ECC is disabled" messages.  16 seem to be a repeat
(is this a serial log ... so we get all the messages up to some point, then see a re-run when the main
console is enabled?).  But it looks like the driver was attempted to be loaded multiple times.

-Tony