[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180522083456.GA5512@pd.tnic>
Date: Tue, 22 May 2018 10:34:56 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>,
Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, linux-edac@...r.kernel.org,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg
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.
Powered by blists - more mailing lists