From: Yazen Ghannam <yazen.ghannam@amd.com>
To: WGH <wgh@torlan.ru>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
bp@alien8.de, Smita.KoralahalliChannabasappa@amd.com
Subject: Re: [PATCH] EDAC/AMD64: Update scrub register addresses for newer models
Date: Wed, 20 Jan 2021 08:35:29 -0600 [thread overview]
Message-ID: <20210120143529.GA1385775@yaz-nikka.amd.com> (raw)
In-Reply-To: <f171c29f-5c89-683c-8cf2-399c9af5153e@torlan.ru>
On Mon, Jan 18, 2021 at 04:30:58AM +0300, WGH wrote:
> On 16/01/2021 17:33, Yazen Ghannam wrote:
> > From: Yazen Ghannam <yazen.ghannam@amd.com>
> >
> > The Family 17h scrubber registers moved to different offset starting
> > with Model 30h. The new register offsets are used for all currently
> > available models since then.
> >
> > Use the new register addresses as the defaults.
> >
> > Set the proper scrub register addresses during module init for older
> > models.
>
> So I tested the patch on my machine (AMD Ryzen 9 3900XT on ASRock B550 Extreme4 motherboard, Linux 5.10.7).
>
> The /sys/devices/system/edac/mc/mc0/sdram_scrub_rate value seems to be stuck at 12284069 right after the boot, and does not change.
> Writes to the file do not report any errors.
>
> dmesg:
>
> [ 0.549451] EDAC MC: Ver: 3.0.0
> [ 0.817576] EDAC amd64: F17h_M70h detected (node 0).
> [ 0.818159] EDAC amd64: Node 0: DRAM ECC enabled.
> [ 0.818717] EDAC amd64: MCT channel count: 2
> [ 0.819324] EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 0000:00:18.3 (INTERRUPT)
> [ 0.819909] EDAC MC: UMC0 chip selects:
> [ 0.819910] EDAC amd64: MC: 0: 16384MB 1: 16384MB
> [ 0.820488] EDAC amd64: MC: 2: 16384MB 3: 16384MB
> [ 0.821067] EDAC MC: UMC1 chip selects:
> [ 0.821067] EDAC amd64: MC: 0: 16384MB 1: 16384MB
> [ 0.821630] EDAC amd64: MC: 2: 16384MB 3: 16384MB
> [ 0.822187] EDAC amd64: using x16 syndromes.
> [ 0.822739] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV 0000:00:18.0 (POLLED)
> [ 0.823314] AMD64 EDAC driver v3.5.0
>
>
Thanks for testing. I'll try to find a similar system and check it out.
Thanks,
Yazen
next prev parent reply other threads:[~2021-01-20 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 14:33 [PATCH] EDAC/AMD64: Update scrub register addresses for newer models Yazen Ghannam
2021-01-18 1:30 ` WGH
2021-01-20 14:35 ` Yazen Ghannam [this message]
2021-01-18 19:31 ` Borislav Petkov
2021-01-20 14:41 ` Yazen Ghannam
2021-01-20 14:50 ` 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=20210120143529.GA1385775@yaz-nikka.amd.com \
--to=yazen.ghannam@amd.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wgh@torlan.ru \
/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