From: Josh Hunt <johunt@akamai.com>
To: Borislav Petkov <bp@amd64.org>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] amd64_edac: Memory size reported double on processor family 0Fh
Date: Fri, 14 Sep 2012 07:55:28 -0500 [thread overview]
Message-ID: <50532940.10201@akamai.com> (raw)
In-Reply-To: <20120912172351.GE12103@aftab.osrc.amd.com>
On 09/12/2012 12:23 PM, Borislav Petkov wrote:
> Ok, I have something preliminary which seems to work fine on my K8 here.
> If you'd like, you can give it a run:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git error-queue
>
> I've changed also debug messages, etc, so pls take a look at those and
> let me know whether they're understandable, make sense, etc, etc.
Boris
Thanks to your help I was able to test your branch, but it still does
not resolve the problem. Removal of the "factor=1" workaround fixes the
memory size reporting on boot, but the sysfs values are still incorrect.
[ 25.836264] EDAC MC: DCT0 chip selects:
[ 25.836266] EDAC amd64: MC: 0: 1024MB 1: 1024MB
[ 25.836398] EDAC amd64: MC: 2: 1024MB 3: 1024MB
[ 25.836530] EDAC amd64: MC: 4: 0MB 5: 0MB
[ 25.836662] EDAC amd64: MC: 6: 0MB 7: 0MB
root@192.168.1.1:/sys/devices/system/edac/mc/mc0# grep . *
ce_count:0
ce_noinfo_count:0
dbam:0x0000000000000022
dhar:0x00000000ee001201
dram_hole:ee000000 12000000 12000000
max_location:csrow 7 channel 1
mc_name:K8
grep: reset_counters: Permission denied
sdram_scrub_rate:761
seconds_since_reset:276
size_mb:8192
topmem:0x00000000ee000000
topmem2:0x0000000112000000
ue_count:0
ue_noinfo_count:0
root@192.168.1.1:/sys/devices/system/edac/mc/mc0/csrow1# grep . *
ce_count:0
ch0_ce_count:0
ch0_dimm_label:mc#0csrow#0channel#1
ch1_ce_count:0
ch1_dimm_label:mc#0csrow#4channel#1
dev_type:Unknown
edac_mode:S4ECD4ED
mem_type:Unbuffered-DDR2
size_mb:2048
ue_count:0
To be sure I'm using the correct branch the last git log entry is:
9d67117feece8852570cc8ee25b68c41f8def323
I could be incorrect, but I still think there's a problem with either a)
ddr2_cs_size() for this cpu, or b) the extra shift left when WIDTH_128
is true.
Josh
next prev parent reply other threads:[~2012-09-14 12:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1347403947-20187-1-git-send-email-johunt@akamai.com>
2012-09-11 23:02 ` [PATCH] amd64_edac: Memory size reported double on processor family 0Fh Josh Hunt
2012-09-12 8:51 ` Borislav Petkov
2012-09-12 12:38 ` Josh Hunt
2012-09-12 12:52 ` Josh Hunt
2012-09-12 15:30 ` Borislav Petkov
2012-09-12 15:37 ` Josh Hunt
2012-09-12 15:49 ` Borislav Petkov
2012-09-12 16:23 ` Josh Hunt
2012-09-12 16:48 ` Borislav Petkov
2012-09-12 16:58 ` Josh Hunt
2012-09-12 17:06 ` Borislav Petkov
2012-09-12 17:23 ` Borislav Petkov
2012-09-14 12:55 ` Josh Hunt [this message]
2012-09-14 14:39 ` Josh Hunt
2012-09-14 15:40 ` Borislav Petkov
2012-09-21 12:36 ` Borislav Petkov
2012-09-21 13:02 ` Josh Hunt
2012-09-21 14:01 ` Borislav Petkov
2012-09-21 14:54 ` Josh Hunt
2012-09-21 15:10 ` 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=50532940.10201@akamai.com \
--to=johunt@akamai.com \
--cc=bp@amd64.org \
--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