mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Gabriel C <nix.or.die@gmail.com>
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:45:25 +0100	[thread overview]
Message-ID: <20180110234524.a5qggzxslvrmi4ul@pd.tnic> (raw)
In-Reply-To: <5be13f07-aeae-ee07-1194-f882eb958ac8@gmail.com>

On Thu, Jan 11, 2018 at 12:31:08AM +0100, Gabriel C wrote:
> 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 first one says *DRAM ECC* is disabled on that node - not the node
itself. Looks like it confuses you too.

> 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.

So this is a purely informational message. There's a lot of messages
like that in the kernel. I still don't understand what your problem is
with this particular one.

> 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.

"ECC disabled in the BIOS or no ECC capability, module will not load." -
I think that sentence is explaining the situation pretty good:

either ECC checking is disabled in the BIOS

or

ECC capability cannot be detected.

What do you think it should say instead?

> So do we need an < fam17h  check for that message then ?

That message says:

"Either enable ECC checking or ..."

That first part refers to the user going into the BIOS and enabling ECC
checking. It says so above too: "ECC disabled in the BIOS".

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2018-01-10 23:45 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
2018-01-10 23:45     ` Borislav Petkov [this message]
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=20180110234524.a5qggzxslvrmi4ul@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@gmail.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®