Re: [GIT PULL] EDAC pile for 5.4 -> AMD family 17h, model 70h support

[Jeff God <jfgaudreault@gmail.com>]

On Mon, 7 Oct 2019 at 03:16, Borislav Petkov <bp@alien8.de> wrote:
>
> Try this as root (the first command is cd-ing into the default debugfs
> mountpoint - check whether that is the case on your system first).
>
> # cd /sys/kernel/debug/mce-inject/
> # echo 10 > /sys/devices/system/machinecheck/machinecheck0/check_interval
> # echo 0x9c7d410092080813 > status; echo 0x000000006d3d483b > addr; echo 2 > cpu; echo hw > flags; echo 4 > bank
>
> If you have this in your dmesg:
>
> [    1.420991] RAS: Correctable Errors collector initialized.
>
> then you need to boot with "ras=cec_disable" first.

Yes, I had to add ras=cec_disable in my case based on dmesg, but after
that the command above still did not output anything to dmesg or any
error.

> > but it does not seem EDAC ever report any ce (or ue) ecc error even
> > when they may be happening and corrected in background.
>
> What does that mean?
>
> You are getting ECCs or you simply want to test whether the ECC
> reporting works on your machine?
>

I want to test that the ECC reporting is working on my machine (so
that when real errors will happen one day I will get notified)

The method I described previously to generate errors by overclocking
memory was my initial method to generate real errors, which proved to
work well on another system with a previous generation AMD Ryzen 2700x
and similar motherboard and same memory, but on this system it does
not report any error, although turning off ECC in the bios showed that
memory corruption is happening fairly quickly in this case, hence the
conclusion that error reporting was probably not working but the
underlying memory error correction system may be working.

Jean-Frederic