From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: Jeff God <jfgaudreault@gmail.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: Thu, 10 Oct 2019 11:54:09 +0200 [thread overview]
Message-ID: <20191010095409.GB7658@zn.tnic> (raw)
In-Reply-To: <724d6f97-61f2-94bd-3f4b-793a55b6ac15@amd.com>
On Wed, Oct 09, 2019 at 08:31:26PM +0000, Ghannam, Yazen wrote:
> Please let me know if this works or not for you. I'll need to do some more
> debug if it doesn't work.
Yah, that did it, thx:
[ 166.317498] mce: Machine check injector initialized
[ 171.734222] mce: do_inject: CPU0, toggling...
[ 175.808430] mce: [Hardware Error]: Machine check events logged
[ 175.808612] [Hardware Error]: Corrected error, no action required.
[ 175.808708] [Hardware Error]: CPU:0 (17:1:2) MC18_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c2040000000011b
[ 175.808831] [Hardware Error]: Error Addr: 0x0000000000000000
[ 175.808920] [Hardware Error]: IPID: 0x000000ff03830400, Syndrome: 0x0000000000000000
[ 175.809023] [Hardware Error]: Platform Security Processor Ext. Error Code: 0, An ECC or parity error in a PSP RAM instance.
[ 175.809143] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD
> I've seen this too, and I'm looking into it. I'm doing some research to find
> the correct (or at least sane) value for current and legacy systems.
/**
* struct edac_raw_error_desc - Raw error report structure
* @grain: minimum granularity for an error report, in bytes
I'm guessing 1 on AMD as the error address reported is on a byte
granularity. Or?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2019-10-10 9:54 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
2019-10-10 9:54 ` Borislav Petkov [this message]
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=20191010095409.GB7658@zn.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--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 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.