mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"bp@alien8.de" <bp@alien8.de>,
	"dougthompson@xmission.com" <dougthompson@xmission.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	"Chrzaniuk, Hubert" <hubert.chrzaniuk@intel.com>,
	"Anaczkowski, Lukasz" <lukasz.anaczkowski@intel.com>
Subject: RE: [PATCH 1/1] EDAC, sb_edac: Fix channel reporting on Knights Landing
Date: Fri, 29 Jul 2016 04:15:15 +0000	[thread overview]
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC0241BC4E@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1469231089-22837-1-git-send-email-lukasz.odzioba@intel.com>

On Saturday, July 23, 2016 1:45 AM, Lukasz Odzioba wrote:
> On Intel Xeon Phi Knights Landing processor family the channels
> of memory controller have untypical arrangement - MC0 is mapped to
> CH3,4,5 and MC1 is mapped to CH0,1,2. This causes EDAC driver to
> report the channel name incorrectly.
>
> We missed this change earlier, so the code already contains
> similar comment, but the translation function is incorrect.
>
> Without this patch:
>  errors in DIMM_A and DIMM_D were reported in DIMM_D
>  errors in DIMM_B and DIMM_E were reported in DIMM_E
>  errors in DIMM_C and DIMM_F were reported in DIMM_F
>
> Fixes: d0cdf9003140 ("sb_edac: Add Knights Landing (Xeon Phi gen 2) support")

Hi,
I would greatly appreciate it if you kindly give me some feedback on this patch.

Thanks,
Lukas

  reply	other threads:[~2016-07-29  4:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 23:44 Lukasz Odzioba
2016-07-29  4:15 ` Odzioba, Lukasz [this message]
2016-08-03  6:44 ` Borislav Petkov
2016-08-03  7:06   ` Chrzaniuk, Hubert
2016-08-03  7:12     ` Borislav Petkov
2016-08-03  7:44       ` Chrzaniuk, Hubert
2016-08-03  7:58         ` Borislav Petkov
2016-08-03  8:54           ` Borislav Petkov
2016-08-03  9:25             ` Chrzaniuk, Hubert
2016-08-03  9:31               ` Borislav Petkov
2016-08-03 10:23                 ` Chrzaniuk, Hubert

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=D6EDEBF1F91015459DB866AC4EE162CC0241BC4E@IRSMSX103.ger.corp.intel.com \
    --to=lukasz.odzioba@intel.com \
    --cc=bp@alien8.de \
    --cc=dougthompson@xmission.com \
    --cc=hubert.chrzaniuk@intel.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.anaczkowski@intel.com \
    --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
all inboxes | Powered by JetHome®