From: Aristeu Rozanski <aris@redhat.com>
To: Justin Ernst <justin.ernst@hpe.com>
Cc: Borislav Petkov <bp@alien8.de>,
russ.anderson@hpe.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Raise maximum number of memory controllers
Date: Wed, 26 Sep 2018 12:13:23 -0400 [thread overview]
Message-ID: <20180926161323.2v4epi622yrknu53@redhat.com> (raw)
In-Reply-To: <20180925143449.284634-1-justin.ernst@hpe.com>
On Tue, Sep 25, 2018 at 09:34:49AM -0500, Justin Ernst wrote:
> We observe an oops in the skx_edac module during boot.
That's happening also on sb_edac too and the oops comes from memory corruption
after trying to load the module several times during boot.
--
Aristeu
next prev parent reply other threads:[~2018-09-26 16:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 14:34 [PATCH] Raise maximum number of memory controllers Justin Ernst
2018-09-25 15:26 ` Borislav Petkov
2018-09-25 17:50 ` Luck, Tony
2018-09-25 18:07 ` Borislav Petkov
2018-09-26 9:35 ` Borislav Petkov
2018-09-26 15:27 ` Borislav Petkov
2018-09-26 16:03 ` Mauro Carvalho Chehab
2018-09-26 16:17 ` Borislav Petkov
2018-09-26 17:39 ` Mauro Carvalho Chehab
2018-09-26 18:10 ` Luck, Tony
2018-09-26 18:23 ` Russ Anderson
2018-09-26 23:02 ` Luck, Tony
2018-09-27 4:52 ` Borislav Petkov
2018-09-27 21:44 ` Luck, Tony
2018-09-27 22:03 ` Borislav Petkov
2018-09-28 1:10 ` Mauro Carvalho Chehab
2018-10-01 12:47 ` Borislav Petkov
2018-10-01 22:43 ` [PATCH] EDAC: Don't add devices under /sys/bus/edac Luck, Tony
2018-10-02 1:22 ` Mauro Carvalho Chehab
2018-10-02 15:51 ` Ernst, Justin
2018-10-02 16:26 ` Borislav Petkov
2018-11-06 14:45 ` Borislav Petkov
2018-11-13 19:09 ` Ernst, Justin
2018-11-13 19:15 ` Borislav Petkov
2018-09-26 7:55 ` [PATCH] Raise maximum number of memory controllers Zhuo, Qiuxu
2018-09-26 13:53 ` Russ Anderson
2018-09-26 16:13 ` Aristeu Rozanski [this message]
2018-09-27 5:56 ` Borislav Petkov
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=20180926161323.2v4epi622yrknu53@redhat.com \
--to=aris@redhat.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=russ.anderson@hpe.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).