From: Toshi Kani <toshi.kani@hpe.com>
To: "mchehab@infradead.org" <mchehab@infradead.org>,
"tony.luck@intel.com" <tony.luck@intel.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: [3/3] EDAC, ghes: Make it a proper module
Date: Wed, 26 Jul 2017 19:24:59 +0000 [thread overview]
Message-ID: <1501096535.2042.76.camel@hpe.com> (raw)
On Wed, 2017-07-26 at 15:17 -0300, Mauro Carvalho Chehab wrote:
> Em Wed, 26 Jul 2017 17:27:12 +0000
:
> I didn't try to inject an error, as I'm not sure if EINJ feature is
> enabled on this BIOS. Probably not.
I believe it has EINJ support.
> At least on this machine, I very much prefer to use sb_edac driver.
>
> As I explained earlier in the previous thread, I just don't if the
> BIOS would be doing the right thing for CE, as I don't know its
> internal algorithm.
>
> Also, as I'm maintaining the EDAC userspace tools (rasdaemon),
> I would really love to get a few CE error reports there from time to
> time, as it could be used to check if rasdaemon is doing do the right
> thing to them.
>
> So, I very much prefer to not have any threshold at all there at
> BIOS.
Using sb_edac does not change the fact that it is FF. I do not think
you'd see normal CEs on your box.
Thanks,
-Toshi
next reply other threads:[~2017-07-26 19:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 19:24 Toshi Kani [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 22:41 [3/3] EDAC, ghes: Make it a proper module Toshi Kani
2017-08-02 3:18 Borislav Petkov
2017-08-02 0:19 Toshi Kani
2017-08-01 9:46 Borislav Petkov
2017-07-31 20:19 Toshi Kani
2017-07-29 6:47 Borislav Petkov
2017-07-28 18:50 Toshi Kani
2017-07-27 5:20 Borislav Petkov
2017-07-26 19:49 Toshi Kani
2017-07-26 18:17 Mauro Carvalho Chehab
2017-07-26 17:27 Luck, Tony
2017-07-26 10:51 Mauro Carvalho Chehab
2017-07-26 10:37 Borislav Petkov
2017-07-26 10:24 Mauro Carvalho Chehab
2017-07-26 8:48 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=1501096535.2042.76.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rjw@rjwysocki.net \
--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).