From: Borislav Petkov <bp@alien8.de>
To: Lukasz Odzioba <lukasz.odzioba@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
dougthompson@xmission.com, mchehab@kernel.org,
tony.luck@intel.com, hubert.chrzaniuk@intel.com,
lukasz.anaczkowski@intel.com
Subject: Re: [PATCH 1/1] EDAC, sb_edac: Fix channel reporting on Knights Landing
Date: Wed, 3 Aug 2016 08:44:43 +0200 [thread overview]
Message-ID: <20160803064443.GA31099@nazgul.tnic> (raw)
In-Reply-To: <1469231089-22837-1-git-send-email-lukasz.odzioba@intel.com>
On Sat, Jul 23, 2016 at 01:44:49AM +0200, 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")
> Signed-off-by: Lukasz Odzioba <lukasz.odzioba@intel.com>
> Signed-off-by: Hubert Chrzaniuk <hubert.chrzaniuk@intel.com>
What is that SOB supposed to mean?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2016-08-03 6:46 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
2016-08-03 6:44 ` Borislav Petkov [this message]
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=20160803064443.GA31099@nazgul.tnic \
--to=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=lukasz.odzioba@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®