From: Gabriel C <nix.or.die@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: EDAC-AMD64: what is the ecc_msg good for ?
Date: Thu, 11 Jan 2018 00:31:08 +0100 [thread overview]
Message-ID: <5be13f07-aeae-ee07-1194-f882eb958ac8@gmail.com> (raw)
In-Reply-To: <20180110231235.a3ts353lzajqywb5@pd.tnic>
On 11.01.2018 00:12, Borislav Petkov wrote:
> On Thu, Jan 11, 2018 at 12:06:49AM +0100, Gabriel C wrote:
>> while doing some testings with a EPYC box I notice
>> these strange messages when a Node is disabled.
>>
>> I really do think the message is confusing since
>> we tell 'Node X: ... disabled' followed by a
>> INFO on the edac driver which tells the driver will not load.
>
> And that is confusing because?
Beacuse we see the following:
[ 4.694948] EDAC amd64: Node 6: DRAM ECC disabled.
[ 4.694949] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
The first one tells the Node is disabled the second is a
KERN INFO message telling the *module* will not load.
Telling then *module* will not load for 'this Node' should be clear for everone.
Don't get me wrong for me is clear what this means , I don't need the
second message at all but I have here folks didn't understand wth that means.
>
>> Also even worse , we suggest to use ecc_enable_override then,
>> which can cause wrose things.. We really should not suggest
>> something like this by default.
>
> That is an remnant from the old times. Family 0x17 and newer doesn't
> allow that anymore.
>
So do we need an < fam17h check for that message then ?
next prev parent reply other threads:[~2018-01-10 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 23:06 Gabriel C
2018-01-10 23:12 ` Borislav Petkov
2018-01-10 23:31 ` Gabriel C [this message]
2018-01-10 23:45 ` Borislav Petkov
2018-01-11 0:27 ` Gabriel C
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=5be13f07-aeae-ee07-1194-f882eb958ac8@gmail.com \
--to=nix.or.die@gmail.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®