Linux EDAC development
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Michael Di Domenico <mdidomenico4@gmail.com>
Cc: linux-edac@vger.kernel.org
Subject: Re: dimm mapping
Date: Wed, 16 Dec 2020 18:15:45 +0100	[thread overview]
Message-ID: <20201216171545.GC6312@zn.tnic> (raw)
In-Reply-To: <CABOsP2POd8UhS5Acfg9Ht8NSpULBFbDX+_iK6BGm3ZNGLdRsaw@mail.gmail.com>

On Wed, Dec 16, 2020 at 12:05:25PM -0500, Michael Di Domenico wrote:
> the problem i'm trying to solve is that when i run edac-util -v i
> don't get the dimm labels.  so when MCE trips it's chore to figure out
> which dimm it actually is when looking at the motherboard.  given that
> dmidecode seems to report the dimm labels, it seems odd that edac
> doesn't use them.  but then again i understand how all that's tied
> together (if at all).

Yeah, the short version is, there's no properly defined way for software
to read out DIMM silkscreen labels on each platform. I highly doubt that
is even possible. Perhaps some SMBUS interfaces or whatnot but firmware
is notoriosly buggy so there's no reliability there.

And, as said before, in some cases one cannot map back the physical
address reported with a DIMM MCE to the actual DIMM.

And, in recent times, OEM vendors do more and more RAS in the firmware
so the kernel doesn't get to even see some errors.

I'm always hoping that I'll be corrected some day but until then that's
the current situation, roughly.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2020-12-16 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 15:06 dimm mapping Michael Di Domenico
2020-12-16 16:34 ` Borislav Petkov
2020-12-16 17:05   ` Michael Di Domenico
2020-12-16 17:15     ` Borislav Petkov [this message]
2020-12-16 17:31       ` Michael Di Domenico

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=20201216171545.GC6312@zn.tnic \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=mdidomenico4@gmail.com \
    /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