Linux EDAC development
 help / color / mirror / Atom feed
From: Orion Poplawski <orion@nwra.com>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: EDAC igen6 error messages at boot
Date: Wed, 2 Nov 2022 08:36:11 -0600	[thread overview]
Message-ID: <5f78ed98-e216-6202-8499-dbc7e4358cc5@nwra.com> (raw)
In-Reply-To: <IA1PR11MB617155E9BCA54DED8687209189309@IA1PR11MB6171.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]

On 10/25/22 23:58, Zhuo, Qiuxu wrote:
>> From: Orion Poplawski <orion@nwra.com>
>>> ...
>>>
>>> Yes, can you try a power cycle on the machine and check whether the
>> error log still occur?
>>> Thanks!
>>
>> Still happens.  Seems to happen all the time.
> 
> Thanks for the feedback.
> 
> Looked like the In-band ECC error log was initialized with the value ~0ULL that
> resulted in the spurious errors.
> 
> I don't have such a machine for debug. Could you please try the attached patch to see
> whether it fixes the spurious errors on driver load? If possible please also open the
> "CONFIG_EDAC_DEBUG=y" kernel configuration for more EDAC debug logs.
> 
> Thanks!
> -Qiuxu

I can confirm that the patch removes the errors from the log:

# dmesg | grep -Fi edac
[    0.979497] EDAC MC: Ver: 3.0.0
[  417.538823] caller igen6_probe+0x176/0x7b0 [igen6_edac] mapping 
multiple BARs
[  417.538876] EDAC MC0: Giving out device to module igen6_edac 
controller Intel_client_SoC MC#0: DEV 0000:00:00.0 (INTERRUPT)
[  417.541597] EDAC MC1: Giving out device to module igen6_edac 
controller Intel_client_SoC MC#1: DEV 0000:00:00.0 (INTERRUPT)
[  417.542186] EDAC igen6: v2.5

However, I forgot to enable the CONFIG_EDAC_DEBUG option - do you still 
need that output?

-- 
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion@nwra.com
Boulder, CO 80301                 https://www.nwra.com/

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3847 bytes --]

  reply	other threads:[~2022-11-02 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 16:08 EDAC igen6 error messages at boot Orion Poplawski
2022-10-25  2:46 ` Zhuo, Qiuxu
2022-10-25  2:58   ` Orion Poplawski
2022-10-25  3:13     ` Zhuo, Qiuxu
2022-10-25 15:28       ` Orion Poplawski
2022-10-26  5:58         ` Zhuo, Qiuxu
2022-11-02 14:36           ` Orion Poplawski [this message]
2022-11-04  5:07             ` Zhuo, Qiuxu

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=5f78ed98-e216-6202-8499-dbc7e4358cc5@nwra.com \
    --to=orion@nwra.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=qiuxu.zhuo@intel.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