From: Borislav Petkov <bp@amd64.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
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:58:45 +0100 [thread overview]
Message-ID: <20110203175845.GC26261@aftab> (raw)
In-Reply-To: <20110203172539.GA1581@gentoo.trippels.de>
On Thu, Feb 03, 2011 at 12:25:39PM -0500, Markus Trippelsdorf wrote:
> 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
Ok thanks, will add your Tested-by: too.
> 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.
Yeah, that table needs to be implemented for proper csrow->edac_mode
assignment. I'll try to get it done soon.
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
prev parent reply other threads:[~2011-02-03 17:57 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
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 [this message]
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=20110203175845.GC26261@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox