linux-kernel - Re: [EDAC-AMD64] Display correct RAM sizes in ganged mode on F10 CPUs

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]

Message-ID: <20110203172539.GA1581@gentoo.trippels.de>
Date:	Thu, 3 Feb 2011 18:25:39 +0100
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Borislav Petkov <bp@...64.org>
Cc:	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	Doug Thompson <dougthompson@...ssion.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [EDAC-AMD64] Display correct RAM sizes in ganged mode on F10 CPUs

On 2011.02.03 at 18:09 +0100, Borislav Petkov wrote:
> On Thu, Feb 03, 2011 at 11:42:03AM -0500, Markus Trippelsdorf wrote:
> > > Of course it doesn't, doh!, we need the DRAM chip selects from the
> > > second DCT too. Can you please run this little script as root so that I
> > > can verify that BIOS is actually programming sensible values in those in
> > > ganged mode? (Yeah, leave your DCT setting to ganged in BIOS).
> > > 
> > > --
> > > #!/bin/bash
> > > 
> > > i=0x140
> > > 
> > > while (( $i <= 0x15c )); do
> > >         reg=$(printf "0x%x" $i)
> > >         setpci -s 18.2 $reg.l
> > >         i=$(($i+4))
> > > done
> > 
> > 00000000
> > 00000000
> > 00000000
> > 00000000
> > 00000000
> > 00000000
> > 00000000
> > 00000000
> 
> Ok, can you please try the following one,

Looks good, many thanks Boris.

EDAC amd64: F10h detected (node 0).
EDAC MC: DCT0 chip selects:
EDAC amd64: MC: 0:  1024MB 1:  1024MB
EDAC amd64: MC: 2:  1024MB 3:  1024MB
EDAC amd64: MC: 4:     0MB 5:     0MB
EDAC amd64: MC: 6:     0MB 7:     0MB
EDAC MC: DCT1 chip selects:
EDAC amd64: MC: 0:  1024MB 1:  1024MB
EDAC amd64: MC: 2:  1024MB 3:  1024MB
EDAC amd64: MC: 4:     0MB 5:     0MB
EDAC amd64: MC: 6:     0MB 7:     0MB

BTW another thing, while I have your attention:

cat /sys/devices/system/edac/mc/mc0/csrow0/edac_mode
prints "S4ECD4ED" aka Chipkill on my system.
But I'm using a revision C Phenom that only supports a x4 symbol size,
while the Kingston ECC DIMMs have a width of x8. So according to
table 77 (page 174) of the "BIOS and Kernel Developer’s Guide" the
system is actually running in SECDED mode and does not provide Chipkill.

-- 
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/