From: Russ Anderson <rja@hpe.com>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
Cc: Justin Ernst <justin.ernst@hpe.com>,
Borislav Petkov <bp@alien8.de>,
"Luck, Tony" <tony.luck@intel.com>,
"russ.anderson@hpe.com" <russ.anderson@hpe.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Raise maximum number of memory controllers
Date: Wed, 26 Sep 2018 08:53:45 -0500 [thread overview]
Message-ID: <20180926135345.rtp2mxm74xe2jvts@hpe.com> (raw)
On Wed, Sep 26, 2018 at 07:55:39AM +0000, Zhuo, Qiuxu wrote:
> Hi Justin,
>
> > [ 3401.987556] EDAC MC15: Giving out device to module skx_edac controller Skylake Socket#1 IMC#1
> Just curious, has the system(two memory controllers per socket) got more than 8 sockets?
> Normally, the number "1" in the above string "Skylake Socekt#1 IMC#1" should be 7 (that was 15/2), but it was 1 here.
Yes, that is from a 32 socket system.
Thanks.
next reply other threads:[~2018-09-26 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 13:53 Russ Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-01 12:47 Raise maximum number of memory controllers Borislav Petkov
2018-09-28 1:10 Mauro Carvalho Chehab
2018-09-27 22:03 Borislav Petkov
2018-09-27 21:44 Luck, Tony
2018-09-27 5:56 Borislav Petkov
2018-09-27 4:52 Borislav Petkov
2018-09-26 23:02 Luck, Tony
2018-09-26 18:23 Russ Anderson
2018-09-26 18:10 Luck, Tony
2018-09-26 17:39 Mauro Carvalho Chehab
2018-09-26 16:17 Borislav Petkov
2018-09-26 16:13 Aristeu Rozanski
2018-09-26 16:03 Mauro Carvalho Chehab
2018-09-26 15:27 Borislav Petkov
2018-09-26 9:35 Borislav Petkov
2018-09-26 7:55 Qiuxu Zhuo
2018-09-25 18:07 Borislav Petkov
2018-09-25 17:50 Luck, Tony
2018-09-25 15:26 Borislav Petkov
2018-09-25 14:34 Justin Ernst
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=20180926135345.rtp2mxm74xe2jvts@hpe.com \
--to=rja@hpe.com \
--cc=bp@alien8.de \
--cc=justin.ernst@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=russ.anderson@hpe.com \
--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).