[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110203164203.GB1594@gentoo.trippels.de>
Date: Thu, 3 Feb 2011 17:42:03 +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 17:36 +0100, Borislav Petkov wrote:
> 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
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
--
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/
Powered by blists - more mailing lists