All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
To: Orion Poplawski <orion@nwra.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: RE: EDAC igen6 error messages at boot
Date: Fri, 4 Nov 2022 05:07:13 +0000	[thread overview]
Message-ID: <IA1PR11MB6171186E46E5DD584B8EDF64893B9@IA1PR11MB6171.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5f78ed98-e216-6202-8499-dbc7e4358cc5@nwra.com>

> From: Orion Poplawski <orion@nwra.com>
> ...
> 
> I can confirm that the patch removes the errors from the log:

Thanks for the confirmation.

> # 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?

No. 
Your confirmation above was enough. 😊

-Qiuxu

      reply	other threads:[~2022-11-04  5:07 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
2022-11-04  5:07             ` Zhuo, Qiuxu [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=IA1PR11MB6171186E46E5DD584B8EDF64893B9@IA1PR11MB6171.namprd11.prod.outlook.com \
    --to=qiuxu.zhuo@intel.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=orion@nwra.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 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.