mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Borislav Petkov <bp@amd64.org>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	Doug Thompson <dougthompson@xmission.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EDAC-AMD64] Display correct RAM sizes in ganged mode on F10 CPUs
Date: Thu, 3 Feb 2011 18:25:39 +0100	[thread overview]
Message-ID: <20110203172539.GA1581@gentoo.trippels.de> (raw)
In-Reply-To: <20110203170932.GB26261@aftab>

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

  reply	other threads:[~2011-02-03 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 21:15 Markus Trippelsdorf
2011-02-01 18:51 ` Borislav Petkov
2011-02-01 19:27   ` Markus Trippelsdorf
2011-02-03 15:17     ` Borislav Petkov
2011-02-03 15:59       ` Markus Trippelsdorf
2011-02-03 16:36         ` Borislav Petkov
2011-02-03 16:42           ` Markus Trippelsdorf
2011-02-03 17:09             ` Borislav Petkov
2011-02-03 17:25               ` Markus Trippelsdorf [this message]
2011-02-03 17:58                 ` 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=20110203172539.GA1581@gentoo.trippels.de \
    --to=markus@trippelsdorf.de \
    --cc=bp@amd64.org \
    --cc=dougthompson@xmission.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®