All of lore.kernel.org
 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 16:47:39 -0500	[thread overview]
Message-ID: <6d9b37f8-e753-8c9e-55b9-547c19b02df2@gmail.com> (raw)
In-Reply-To: <7acbeaaf-27cf-0c04-5979-b362f770bc00@gmail.com>

On 2020-01-04 15:03, Jean-Frederic wrote:
> 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)
It seems after all that the real fix may be in on of the last bios update I've
applied, because I retested with kernel 5.4.2 and even 5.4.0 and I now
get also error reporting there, although there is some call stack trace
logged in dmesg, so the newer kernel > 5.4.2 appear much cleaner in
logging at least.

Also now when I do rdmsr 0xC0002003 it returns non-zero, which
wasn't the case before.

-- 
Jean-Frédéric


  reply	other threads:[~2020-01-04 21:47 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
2020-01-04 21:47                                       ` Jean-Frederic [this message]
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=6d9b37f8-e753-8c9e-55b9-547c19b02df2@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.