From: Jean-Frederic <jfgaudreault@gmail.com>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>, Borislav Petkov <bp@alien8.de>
Cc: "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: Fri, 18 Oct 2019 19:08:32 -0400 [thread overview]
Message-ID: <f5820b41-c97a-b6be-df97-bbff85a7e5ee@gmail.com> (raw)
In-Reply-To: <79bca0d0-42eb-c232-6bbe-a958734e096d@gmail.com>
On 2019-10-10 9:04 p.m., Jean-Frederic wrote:
> On 2019-10-10 3:00 p.m., Ghannam, Yazen wrote:
>> 1) rdmsr 0xC0002003
> This returns 0 for me, so I guess PFEH is enabled.
> As long as this is only for the error injection, and is not preventing
> the actual capability for the OS to report the memory errors.
> I'm still not clear on that part.
On 2019-10-10 5:56 a.m., Borislav Petkov wrote:
> On 2019-10-09 7:54 p.m., Jeff God wrote:
>> Would this setting also prevent error reporting at the OS level or is
>> it just related to the injection?
> Platform first error handling meands, the BIOS gets to see the error
> first. So it depends. Yazen, do you have the whole PFEH functionality
> documented somewhere?
>
I don't know if there has been any new information related to these last
points, I am really looking to understand if ECC error reporting will be
working in this new Kernel 5.4 for AMD Ryzen 3900x (or are we saying maybe
this issue could be related to the motherboard?)
In any case, I think EDAC needs to be able to tell us (like at boot time)
if the ECC error reporting is working on the system or not, because right
now (in 5.4) everything appear to load successfully (according to dmesg)
with all the memory information identified, and edac-util tool appear
to be working (and returning zeros).
I don't mind if the error injection part is not working, I think it is
more an enterprise or debugging feature.
Also, since this was working on the previous generation as mentioned before
(i.e. AMD RYZEN 2700X and ASUS PRIME 470 to be more specific), I thought
it would be natural that it works on the newer gen, given the
information/hype provided around launch time.Asus also confirmed to me
through their support that this new motherboard supports ecc. It also has
an ECC option in the bios, as I've mentioned, to enable or disable ecc.
If nobody know the answer to my question, then that is fine, I just
wasn't sure if it was forgotten.
Thanks,
--
Jean-Frédéric
next prev parent reply other threads:[~2019-10-18 23:08 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 [this message]
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=f5820b41-c97a-b6be-df97-bbff85a7e5ee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.