linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Frederic <jfgaudreault@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [GIT PULL] EDAC pile for 5.4 -> AMD family 17h, model 70h support
Date: Sat, 4 Jan 2020 15:03:59 -0500	[thread overview]
Message-ID: <7acbeaaf-27cf-0c04-5979-b362f770bc00@gmail.com> (raw)
In-Reply-To: <fddfb084-69a0-a913-f750-ef0a7830dd1e@gmail.com>

Just to let you know, I have installed the kernel 5.4.7 (with RAS disabled as
usual) and now I can finally see errors reported for the first time very quickly
under serious memory overclocking conditions.

I've used the same test conditions I had before:
4 memory modules at 3600MHz 1.2V, 22,22,22,43 (Kingston KSM26ED8/16ME 16GB 2666MHz 1.2V)
However now it works fine and reports errors (all CE so far). I got 8 CE in less
than 30 minutes using mprime and my original method described before.
edac-util output:
mc0: csrow2: mc#0csrow#2channel#0: 3 Corrected Errors
mc0: csrow3: mc#0csrow#3channel#0: 1 Corrected Errors
mc0: csrow3: mc#0csrow#3channel#1: 4 Corrected Errors

dmesg example:
[ 1561.272106] mce: [Hardware Error]: Machine check events logged
[ 1561.272106] [Hardware Error]: Corrected error, no action required.
[ 1561.272108] [Hardware Error]: CPU:0 (17:71:0) MC18_STATUS[Over|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0xdc2040000000011b
[ 1561.272111] [Hardware Error]: Error Addr: 0x00000004e09173c0
[ 1561.272111] [Hardware Error]: IPID: 0x0000009600150f00, Syndrome: 0x000040000a801103
[ 1561.272113] [Hardware Error]: Unified Memory Controller Ext. Error Code: 0, DRAM ECC error.
[ 1561.272119] EDAC MC0: 1 CE Cannot decode normalized address on mc#0csrow#3channel#1 (csrow:3 channel:1 page:0x0 offset:0x0 grain:64 syndrome:0x4000)
[ 1561.272119] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD

Anyway, thanks again for all the previous information and work done,
I just wanted to confirm that it appears to be working fine on my side now.

I'm not too sure I understand what was the exact problem but it really seems
fine now. I also updated my bios meanwhile but it did not mention there was
anything related to memory or ECC fix. It just said Improve system
performance.
(bios version 1405 for Asus PRIME X570-PRO with Ryzen 3900x)


Best regards,

-- 
Jean-Frédéric


  parent reply	other threads:[~2020-01-04 20:04 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
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 [this message]
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=7acbeaaf-27cf-0c04-5979-b362f770bc00@gmail.com \
    --to=jfgaudreault@gmail.com \
    --cc=Yazen.Ghannam@amd.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).