From: Borislav Petkov <bp@alien8.de>
To: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
Cc: Tony Luck <tony.luck@intel.com>,
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: Sun, 20 May 2018 22:40:32 +0200 [thread overview]
Message-ID: <20180520204032.GA19845@pd.tnic> (raw)
In-Reply-To: <CAG=yYwk-dbMF_7eS9bUraAru8b4fyCosxp+MpQA=1ZYH0nd_hg@mail.gmail.com>
On Sun, May 20, 2018 at 05:27:32PM +0530, Jeffrin Thalakkottoor wrote:
> output for "dmesg | mcelog --ascii" command related
Ok, but please do not top-post.
...
> Hardware event. This is not a software error.
> CPU 0 BANK 0 TSC dead
> STATUS 0 MCGSTATUS 0
> line timer enabled
> smpboot: CPU0: Intel(R) Pentium(R) CPU 3825U @ 1.90GHz (family: 0x6,
> model: 0x3d, stepping: 0x4)
> Machine check events logged
> Hardware event. This is not a software error.
> CPU 0 BANK 0
> TIME 1526815774 Sun May 20 16:59:34 2018
> MCG status:
> MCi status:
> Machine check not valid
> Corrected error
> MCA: No Error
> STATUS 0 MCGSTATUS 0
> CPUID Vendor Intel Family 6 Model 61
> (Fields were incomplete)
Looks like mcelog has trouble decoding this. Have you updated mcelog to
the latest version in your distro?
> SOCKET 0 APIC 0 microcode 2a
@Tony, I'm hoping you'll be more successful in decoding the error by
hand.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-05-20 20:41 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 [this message]
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
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=20180520204032.GA19845@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).