linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Andersson <pipatron@gmail.com>
To: linux-edac@vger.kernel.org
Subject: User question about memory scrubbing
Date: Thu, 18 Jun 2020 18:49:45 +0200	[thread overview]
Message-ID: <CAKkunMbNWppx_i6xSdDHLseA2QQmGJqj_crY=NF-GZML5np4Vw@mail.gmail.com> (raw)

Hi! I realize that this is more of a developer-to-developer list, but
I'm a hobbyist who recently bought my first system with ECC RAM
(Opteron 6386 SE) and I can't get memory scrubbing to work. It's hard
to find people who know anything about it.

Preliminary research led me to the EDAC documentation on
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-edac
and in particular the "sdram_scrub_rate" file, but had no luck
manipulating it.

Before I'm getting too lost: Is that the right way to configure it?

I have amd64_edac_mod and edac_mce_amd loaded. I briefly looked at
amd64_edac.c and it appears to have the necessary code and matches the
documentation from AMD so there's something I'm not doing right. I did
post a more elaborate question on
https://unix.stackexchange.com/questions/593060/how-do-i-enable-and-verify-ecc-ram-scrubbing-in-linux
but I'm afraid it's too technical for most users (too technical for me
too apparently!)

Hints and pointers welcome,
Anders

             reply	other threads:[~2020-06-18 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 16:49 Anders Andersson [this message]
2020-06-18 17:56 ` User question about memory scrubbing Borislav Petkov
2020-06-18 18:40   ` [PATCH] EDAC/amd64: Read back the scrub rate PCI register on F15h Borislav Petkov
2020-06-22 15:13     ` Borislav Petkov
2020-06-23  1:41       ` Anders Andersson
2020-06-23  9:18         ` Borislav Petkov
2020-06-19  1:55   ` User question about memory scrubbing Anders Andersson

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='CAKkunMbNWppx_i6xSdDHLseA2QQmGJqj_crY=NF-GZML5np4Vw@mail.gmail.com' \
    --to=pipatron@gmail.com \
    --cc=linux-edac@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;
as well as URLs for NNTP newsgroup(s).