From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>,
Thomas Gleixner <tglx@linutronix.de>,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-edac@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg
Date: Tue, 22 May 2018 10:34:56 +0200 [thread overview]
Message-ID: <20180522083456.GA5512@pd.tnic> (raw)
In-Reply-To: <20180522000614.GA21542@agluck-desk>
On Mon, May 21, 2018 at 05:06:14PM -0700, Luck, Tony wrote:
> On Tue, May 22, 2018 at 02:43:37AM +0530, Jeffrin Thalakkottoor wrote:
> > mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 5: ee0000000040110b
> > mce: [Hardware Error]: TSC 0 ADDR 160000080 MISC 5040008086
> > mce: [Hardware Error]: PROCESSOR 0:306d4 TIME 1526932210 SOCKET 0 APIC
> > 0 microcode 2a
>
> The problem is that "mcelog --ascii" is expecting the first line to
> look like:
>
> CPU 0: Machine Check Exception: 0 Bank 5: ee0000000040110b
>
> This seems to have been broken by commit:
>
> cd9c57cad3fe ("x86/MCE: Dump MCE to dmesg if no consumers")
>
> relevent part is this ... where we now conditionally include the
> word "Exception".
Well, mcelog should decode the error signature regardless whether it
says "Exception" or not, IMO.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-05-22 8:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:49 PROBLEM: mce: [Hardware Error] from dmesg -l emerg Jeffrin Thalakkottoor
2018-05-14 16:27 ` Borislav Petkov
2018-05-14 16:50 ` Luck, Tony
2018-05-20 11:00 ` Jeffrin Thalakkottoor
2018-05-20 11:57 ` Jeffrin Thalakkottoor
2018-05-20 20:40 ` Borislav Petkov
2018-05-21 12:01 ` Jeffrin Thalakkottoor
2018-05-21 16:58 ` Luck, Tony
2018-05-21 20:11 ` Jeffrin Thalakkottoor
2018-05-21 20:57 ` Luck, Tony
2018-05-21 21:13 ` Jeffrin Thalakkottoor
2018-05-22 0:06 ` Luck, Tony
2018-05-22 8:34 ` Borislav Petkov [this message]
2018-05-22 13:16 ` Jeffrin Thalakkottoor
2018-05-21 20:19 ` 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=20180522083456.GA5512@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jeffrin@rajagiritech.edu.in \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).