All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Borislav Petkov <bp@amd64.org>,
	"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 17:36:00 +0100	[thread overview]
Message-ID: <20110203163600.GA26261@aftab> (raw)
In-Reply-To: <20110203155951.GA1594@gentoo.trippels.de>

On Thu, Feb 03, 2011 at 10:59:52AM -0500, Markus Trippelsdorf wrote:
> Hm, that doesn't work:
> 
> 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:     0MB 1:     0MB
> EDAC amd64: MC: 2:     0MB 3:     0MB
> EDAC amd64: MC: 4:     0MB 5:     0MB
> EDAC amd64: MC: 6:     0MB 7:     0MB
> EDAC amd64: using x4 syndromes.

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
--

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-02-03 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 21:15 [EDAC-AMD64] Display correct RAM sizes in ganged mode on F10 CPUs 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 [this message]
2011-02-03 16:42           ` Markus Trippelsdorf
2011-02-03 17:09             ` Borislav Petkov
2011-02-03 17:25               ` Markus Trippelsdorf
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=20110203163600.GA26261@aftab \
    --to=bp@amd64.org \
    --cc=dougthompson@xmission.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.