From: Borislav Petkov <bp@alien8.de>
To: Jeff God <jfgaudreault@gmail.com>
Cc: linux-edac@vger.kernel.org
Subject: Re: [GIT PULL] EDAC pile for 5.4 -> AMD family 17h, model 70h support
Date: Mon, 7 Oct 2019 09:16:45 +0200 [thread overview]
Message-ID: <20191007071502.GA24289@zn.tnic> (raw)
In-Reply-To: <CAEVokG7UmudOALmeTBq2NgFSiZyGq_6b58nHt2UUHAM2Mzbw+Q@mail.gmail.com>
On Sat, Oct 05, 2019 at 12:52:15PM -0400, Jeff God wrote:
> * I tried different addr values that I believe are in valid range, all
> other values (cpu,...) were left to their default (0), I used bank 0
> to trigger the tests and tried different values briefly but always
> with the same results
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.
> 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?
P.S., Please do not top-post and see if you get another mail client -
gmail is linewrapping dmesg and is generally bad for pasting logs and
code in.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-10-07 7:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEVokG7TeAbmkhaxiTpsxhv1pQzqRpU=mR8gVjixb5kXo3s2Eg@mail.gmail.com>
[not found] ` <20190924092644.GC19317@zn.tnic>
2019-10-05 16:52 ` [GIT PULL] EDAC pile for 5.4 -> AMD family 17h, model 70h support Jeff God
2019-10-07 7:16 ` Borislav Petkov [this message]
2019-10-07 12:58 ` Jeff God
2019-10-08 11:50 ` Borislav Petkov
2019-10-08 19:42 ` Ghannam, Yazen
2019-10-08 23:08 ` Jeff God
2019-10-09 10:30 ` Borislav Petkov
2019-10-09 20:31 ` Ghannam, Yazen
2019-10-09 23:54 ` Jeff God
2019-10-10 9:56 ` Borislav Petkov
2019-10-10 12:48 ` Jean-Frederic
2019-10-10 13:41 ` Borislav Petkov
2019-10-10 19:00 ` Ghannam, Yazen
2019-10-11 1:04 ` Jean-Frederic
2019-10-18 23:08 ` Jean-Frederic
2019-10-19 8:25 ` Borislav Petkov
2019-10-19 16:12 ` Jean-Frederic
2019-10-21 14:24 ` Ghannam, Yazen
2020-01-04 20:03 ` Jean-Frederic
2020-01-04 21:47 ` Jean-Frederic
2019-10-10 9:54 ` 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=20191007071502.GA24289@zn.tnic \
--to=bp@alien8.de \
--cc=jfgaudreault@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).