From: "Raj, Ashok" <ashok.raj@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Borislav Petkov <bp@alien8.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Len Brown <len.brown@intel.com>, Tony Luck <tony.luck@intel.com>,
ashok.raj@intel.com
Subject: Re: Dell XPS13: MCE (Hardware Error) reported
Date: Mon, 9 Jan 2017 11:23:36 -0800 [thread overview]
Message-ID: <20170109192336.GA42856@otc-nc-03> (raw)
In-Reply-To: <662102c9-94da-3193-08c4-9fe75411cadb@molgen.mpg.de>
Hi Paul
On Mon, Jan 09, 2017 at 12:53:33PM +0100, Paul Menzel wrote:
>
>
> On 01/05/17 02:12, Raj, Ashok wrote:
>
> >>>CPUID Vendor Intel Family 6 Model 142
> >This is Kabylake Mobile
> >
> >>>Hardware event. This is not a software error.
> >>>MCE 1
> >>>CPU 0 BANK 7
> >>>MISC 7880018086 ADDR fef1ce40
> >>>TIME 1483543069 Wed Jan 4 16:17:49 2017
> >>>STATUS ee0000000040110a MCGSTATUS 0
> >
> >Decoding the bits further from MCi_STATUS above:
> >Val=1, OVER=1, UC=1, but EN=0 indicates this isn't a MCE, hence should have
> >been signaled by a CMCI.
> >
> >PCC=1, but should be ignored when EN=0.
> >MCACOD: 110a MSCOD: 0040
This MSCOD indicates that its a write back access to mmio space. Its possible
that BIOS is scanning certain memory region during boot. During which time
BIOS does disable generation of MCE's. Which is why EN=0 in the above log.
Its a BIOS bug, one would expect that BIOS clears up these before handoff to
OS. During OS boot we also scan all MC banks and log/clear them.
If you aren't observing them during normal operation you can safely ignore
these preboot logs, or pass them along to your OEM.
Cheers,
Ashok
next prev parent reply other threads:[~2017-01-09 19:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 15:42 Dell XPS13: MCE (Hardware Error) reported Paul Menzel
2017-01-04 22:55 ` Borislav Petkov
2017-01-05 1:12 ` Raj, Ashok
2017-01-09 11:53 ` Paul Menzel
2017-01-09 19:23 ` Raj, Ashok [this message]
2017-01-27 13:35 ` Paul Menzel
2017-01-27 17:10 ` Borislav Petkov
2017-01-27 17:16 ` Mario.Limonciello
2017-01-31 15:29 ` Paul Menzel
2017-01-31 17:20 ` Borislav Petkov
2017-01-31 18:50 ` Austin S. Hemmelgarn
2017-02-01 20:52 ` Mario.Limonciello
2017-01-05 5:00 Daniel J Blueman
2017-01-05 14:05 ` Daniel J Blueman
2017-01-05 20:10 ` Alexander Alemayhu
2017-01-05 20:31 ` Borislav Petkov
2017-01-05 20:43 ` Raj, Ashok
2017-01-05 21:03 ` Pandruvada, Srinivas
2017-01-05 23:23 ` Alexander Alemayhu
2017-01-05 21:38 ` Alexander Alemayhu
2017-01-05 23:28 ` Raj, Ashok
2017-01-05 23:56 ` Borislav Petkov
2017-01-06 1:26 ` Raj, Ashok
2017-01-06 11:16 ` Borislav Petkov
2017-01-06 15:58 ` Raj, Ashok
2017-01-06 16:54 ` Borislav Petkov
2017-01-06 17:04 ` Raj, Ashok
2017-01-09 10:55 ` Paul Menzel
2017-01-09 11:05 ` Borislav Petkov
2017-01-09 11:11 ` Paul Menzel
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=20170109192336.GA42856@otc-nc-03 \
--to=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=pmenzel@molgen.mpg.de \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.