linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Andersson <pipatron@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org
Subject: Re: User question about memory scrubbing
Date: Fri, 19 Jun 2020 03:55:16 +0200	[thread overview]
Message-ID: <CAKkunMaXyw+U-izfgXRuhN1tafjXksw_6rsMB82xv=zseFgkqA@mail.gmail.com> (raw)
In-Reply-To: <20200618175646.GD27951@zn.tnic>

On Thu, Jun 18, 2020 at 7:56 PM Borislav Petkov <bp@alien8.de> wrote:
>
> On Thu, Jun 18, 2020 at 06:49:45PM +0200, Anders Andersson wrote:
> > 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.
>
> Oh, you're manipulating it alright but there's a bug in reporting it.
> Wanna test a patch?

Wow, nice to see that I'm not crazy, and thanks for the quick fix! I
saw the patch and I will try it out after I've re-learnt how to build
a kernel again. It's been well over 10 years since I last had to...

// Anders

      parent reply	other threads:[~2020-06-19  1:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 16:49 User question about memory scrubbing Anders Andersson
2020-06-18 17:56 ` 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   ` Anders Andersson [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='CAKkunMaXyw+U-izfgXRuhN1tafjXksw_6rsMB82xv=zseFgkqA@mail.gmail.com' \
    --to=pipatron@gmail.com \
    --cc=bp@alien8.de \
    --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).