From: Borislav Petkov <bp@alien8.de>
To: Daniel Aberger - Profihost AG <d.aberger@profihost.ag>
Cc: tony.luck@intel.com, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, s.priebe@profihost.ag,
n.fahldieck@profihost.ag, p.kramme@profihost.ag
Subject: Re: MCE reports errors that can't be verified
Date: Mon, 29 Oct 2018 17:15:25 +0100 [thread overview]
Message-ID: <20181029161525.GI32150@zn.tnic> (raw)
In-Reply-To: <6ccf5413-ce2a-bbb9-0203-b0cc9fe2e641@profihost.ag>
On Mon, Oct 29, 2018 at 11:45:04AM +0100, Daniel Aberger - Profihost AG wrote:
...
> [Mi Aug 22 13:54:47 2018] mce: [Hardware Error]: CPU 15: Machine Check:
> 0 Bank 7: cc00008000010091
> [Mi Aug 22 13:54:47 2018] mce: [Hardware Error]: TSC 0 ADDR 70fb1b3ec0
> MISC 142189886
> [Mi Aug 22 13:54:47 2018] mce: [Hardware Error]: PROCESSOR 0:306f2 TIME
> 1534938887 SOCKET 1 APIC 26 microcode 3d
The fact that you see this, means, the error has reached the last
notifier. So the EDAC notifier must've run too and handed the error to
the EDAC driver.
Can you send a full dmesg from that machine, privately to Tony and me is
fine too.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-10-29 16:15 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 [this message]
2018-10-29 16:59 ` Luck, Tony
2018-10-29 17:51 ` Borislav Petkov
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=20181029161525.GI32150@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