linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Aristeu Rozanski <aris@redhat.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Koba Ko <koba.ko@canonical.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/1] EDAC/i10nm: Skip the absent memory controllers
Date: Fri, 7 Jul 2023 06:38:05 +0000	[thread overview]
Message-ID: <CY8PR11MB71343D8C5C1AEEB1604FCFEB892DA@CY8PR11MB7134.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAAd53p6J8usSi+rHnd9+714mUqZ2zTdhFSEWUtiK7aNzcAZ8CA@mail.gmail.com>

> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ...
> Subject: Re: [PATCH 1/1] EDAC/i10nm: Skip the absent memory controllers
> 
> On Thu, Jul 6, 2023 at 9:46 PM Qiuxu Zhuo <qiuxu.zhuo@intel.com> wrote:
> >
> > Some Sapphire Rapids workstations' absent memory controllers still
> > appear as PCIe devices that fool the i10nm_edac driver and result in
> > "shift exponet -66 is negative" call traces from skx_get_dimm_info().
> >
> > Skip the absent memory controllers to avoid the call traces.
> >
> > Reported-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ...
> Tested-by: Kai-Heng Feng <kai.heng.feng@canonical.com>

Thanks for the testing feedback.

-Qiuxu

  reply	other threads:[~2023-07-07  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 13:42 [PATCH 1/1] EDAC/i10nm: Skip the absent memory controllers Qiuxu Zhuo
2023-07-07  5:30 ` Kai-Heng Feng
2023-07-07  6:38   ` Zhuo, Qiuxu [this message]
2023-07-10  1:32   ` [PATCH v2 " Qiuxu Zhuo
2023-07-24 16:09     ` Luck, Tony

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=CY8PR11MB71343D8C5C1AEEB1604FCFEB892DA@CY8PR11MB7134.namprd11.prod.outlook.com \
    --to=qiuxu.zhuo@intel.com \
    --cc=aris@redhat.com \
    --cc=bp@alien8.de \
    --cc=kai.heng.feng@canonical.com \
    --cc=koba.ko@canonical.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).