Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1568356 > unrolled thread
| Started by | Paul Menzel <pmenzel@molgen.mpg.de> |
|---|---|
| First post | 2017-01-27 14:40 +0100 |
| Last post | 2017-01-27 18:20 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Dell XPS13: MCE (Hardware Error) reported Paul Menzel <pmenzel@molgen.mpg.de> - 2017-01-27 14:40 +0100
RE: Dell XPS13: MCE (Hardware Error) reported <Mario.Limonciello@dell.com> - 2017-01-27 18:20 +0100
Re: Dell XPS13: MCE (Hardware Error) reported Borislav Petkov <bp@alien8.de> - 2017-01-27 18:20 +0100
| From | Paul Menzel <pmenzel@molgen.mpg.de> |
|---|---|
| Date | 2017-01-27 14:40 +0100 |
| Subject | Re: Dell XPS13: MCE (Hardware Error) reported |
| Message-ID | <t4eUV-4Ja-1@gated-at.bofh.it> |
Dear Ashok, On 01/09/17 20:23, Raj, Ashok wrote: > 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. Thank you very much for your help. After wasting my time with the Dell support over Twitter [1], where they basically also make you jump through hoops, and then claim it’s an mcelog issue – as they apparently only execute `sudo mcelog` –, I updated to the latest firmware 1.3.2 released yesterday [2]. With that new firmware version, it looks like that the firmware has been fixed and Linux does not report any MCEs. It’d be great if other Dell XPS13 9360 users could verify that. Kind regards, Paul [1] https://twitter.com/pmenzel_molgen/status/818808708692115456 [2] XPS_9360_1.3.2.exe
[toc] | [next] | [standalone]
| From | <Mario.Limonciello@dell.com> |
|---|---|
| Date | 2017-01-27 18:20 +0100 |
| Message-ID | <t4ilP-6Xe-3@gated-at.bofh.it> |
| In reply to | #1568356 |
> -----Original Message----- > From: Borislav Petkov [mailto:bp@alien8.de] > Sent: Friday, January 27, 2017 11:11 AM > To: Paul Menzel <pmenzel@molgen.mpg.de> > Cc: Ashok Raj <ashok.raj@intel.com>; 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>; > Limonciello, Mario <Mario_Limonciello@Dell.com> > Subject: Re: Dell XPS13: MCE (Hardware Error) reported > > On Fri, Jan 27, 2017 at 02:35:16PM +0100, Paul Menzel wrote: > > Thank you very much for your help. After wasting my time with the Dell > > support over Twitter [1], where they basically also make you jump > > through hoops, > > Fun read that twitter page. Especially the bit about not supporting Linux but > but you did ship this laptop with ubuntu. LOOL. > > FWIW, this is not the first time I've heard vendors trying to get away from > dealing with bugs by playing the "we-dont-support-Linux" card. > > Good to know when I go looking for a new laptop in the future. > > -- > Regards/Gruss, > Boris. > > Good mailing practices for 400: avoid top-posting and trim the reply. Sorry you had that experience. I'll pass that on to get that messaging corrected. The team that does Linux support doesn't use twitter, they do phone and email support only. I'm glad you got things sorted moving to the next FW version.
[toc] | [prev] | [next] | [standalone]
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2017-01-27 18:20 +0100 |
| Message-ID | <t4ilP-6Xe-5@gated-at.bofh.it> |
| In reply to | #1568356 |
On Fri, Jan 27, 2017 at 02:35:16PM +0100, Paul Menzel wrote:
> Thank you very much for your help. After wasting my time with the Dell
> support over Twitter [1], where they basically also make you jump through
> hoops,
Fun read that twitter page. Especially the bit about not supporting
Linux but but you did ship this laptop with ubuntu. LOOL.
FWIW, this is not the first time I've heard vendors trying to get away
from dealing with bugs by playing the "we-dont-support-Linux" card.
Good to know when I go looking for a new laptop in the future.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web