From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Daniel Aberger - Profihost AG <d.aberger@profihost.ag>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"s.priebe@profihost.ag" <s.priebe@profihost.ag>,
"n.fahldieck@profihost.ag" <n.fahldieck@profihost.ag>,
"p.kramme@profihost.ag" <p.kramme@profihost.ag>
Subject: Re: MCE reports errors that can't be verified
Date: Mon, 29 Oct 2018 18:51:29 +0100 [thread overview]
Message-ID: <20181029175129.GL32150@zn.tnic> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7D43AA76@ORSMSX110.amr.corp.intel.com>
On Mon, Oct 29, 2018 at 04:59:44PM +0000, Luck, Tony wrote:
> The EDAC driver printed out those messages,
I don't think so - that's __print_mce() in mce.c which dumps the three
lines under "... events logged". Which means, that's the lowest prio,
fallback notifier which runs when nothing else before it has done any
logging.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-10-29 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 10:45 MCE reports errors that can't be verified Daniel Aberger - Profihost AG
2018-10-29 16:15 ` Borislav Petkov
2018-10-29 16:59 ` Luck, Tony
2018-10-29 17:51 ` Borislav Petkov [this message]
2018-10-29 18:25 ` Luck, Tony
2018-10-30 7:22 ` Daniel Aberger - Profihost AG
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=20181029175129.GL32150@zn.tnic \
--to=bp@alien8.de \
--cc=d.aberger@profihost.ag \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=n.fahldieck@profihost.ag \
--cc=p.kramme@profihost.ag \
--cc=s.priebe@profihost.ag \
--cc=tony.luck@intel.com \
--cc=x86@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