Linux EDAC development
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: tibor.gyori@chem.u-szeged.hu
Cc: linux-edac@vger.kernel.org
Subject: Re: Meaning of negative memory_channel value in rasdaemon message
Date: Tue, 15 Feb 2022 16:58:56 +0000	[thread overview]
Message-ID: <Ygvb0MclEFfDNqnQ@yaz-ubuntu> (raw)
In-Reply-To: <20220211234058.81443i8317qnq77e@webmail.u-szeged.hu>

On Fri, Feb 11, 2022 at 11:40:58PM +0100, tibor.gyori@chem.u-szeged.hu wrote:
> Dear EDAC list,
> 
> when rasdaemon reports a memory error, what does it mean for the
> memory_channel value to be negative?
> 
> Example:
> Feb 11 22:34:40 CRD-MILAN-3 rasdaemon[918]:            <...>-42552 [001]
> 0.007845: mce_record:           2022-02-11 22:34:40 +0100 Unified Memory
> Controller (bank=18), status= 9c2040000000011b, Corrected error, no action
> required., mci=CECC, mca= DRAM ECC error.
> Feb 11 22:34:40 CRD-MILAN-3 rasdaemon[918]:  Memory Error 'mem-tx: generic
> read, tx: generic, level: L3/generic', memory_channel=-1,csrow=3, cpu_type=
> AMD Scalable MCA, cpu= 1, socketid= 0, misc= d01a0c7b01000000, addr=
> 2fa07780, synd= e4da80000a800603, ipid= 9600350f00, mcgstatus=0, mcgcap=
> 118, apicid= 1
> 
> Is -1 a magic value for memory_channel? On the AMD Milan platform, I would
> expect that memory channels would be numbered from 0 to 7. I googled for a
> bit, but could not find where this sort of stuff would be documented.
> 

Hi Tibor,

Which version of rasdaemon are you using?

You may be missing the following commit which is including v0.6.7.

https://github.com/mchehab/rasdaemon/commit/854364ba44aee9bc5646f6537fc744b0b54aff37

Thanks,
Yazen


  reply	other threads:[~2022-02-15 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 22:40 Meaning of negative memory_channel value in rasdaemon message tibor.gyori
2022-02-15 16:58 ` Yazen Ghannam [this message]
2022-02-25 15:12   ` tibor.gyori

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=Ygvb0MclEFfDNqnQ@yaz-ubuntu \
    --to=yazen.ghannam@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=tibor.gyori@chem.u-szeged.hu \
    /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