Hi Paul,
> Mario, there are at least two more firmware bugs [4][5][6]. Having fast
> suspend and resume says something about the quality of a device. If the Dell
> XPS13 9360 is supposed to compete with Apple devices, and Google
> Chromebooks, then this should be improved in my opinion. Do you
Hi Paul,
> Mario, there are at least two more firmware bugs [4][5][6]. Having fast
> suspend and resume says something about the quality of a device. If the Dell
> XPS13 9360 is supposed to compete with Apple devices, and Google
> Chromebooks, then this should be improved in my opinion. Do you
<ashok@intel.com>; Linux Kernel Mailing List ; Thorsten Leemhuis <li...@leemhuis.info>; Len
Brown <len.br...@intel.com>; Tony Luck <tony.l...@intel.com>;
Limonciello, Mario <mario_limoncie...@dell.com>
Subject: Re: Dell XPS13: MCE (Hardware Error) reported
On F
; Thorsten Leemhuis ; Len
Brown ; Tony Luck ;
Limonciello, Mario
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
On Tue, Jan 31, 2017 at 04:29:51PM +0100, Paul Menzel wrote:
> Unfortunately, there are not a lot of options. If you know a good
> vendor, please share.
What I'd do is go to the store with a live CD and boot it on the
machine. Using a fairly recent allmodconfig kernel should be able to
tell you
On Tue, Jan 31, 2017 at 04:29:51PM +0100, Paul Menzel wrote:
> Unfortunately, there are not a lot of options. If you know a good
> vendor, please share.
What I'd do is go to the store with a live CD and boot it on the
machine. Using a fairly recent allmodconfig kernel should be able to
tell you
rnel Mailing List ; Thorsten Leemhuis <li...@leemhuis.info>; Len
Brown <len.br...@intel.com>; Tony Luck <tony.l...@intel.com>;
Limonciello, Mario <mario_limoncie...@dell.com>
Subject: Re: Dell XPS13: MCE (Hardware Error) reported
On Fri, Jan 27, 2017 at 02:35:16PM +0100, Pau
Luck ;
Limonciello, Mario
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
uis <li...@leemhuis.info>; Len
> Brown <len.br...@intel.com>; Tony Luck <tony.l...@intel.com>;
> Limonciello, Mario <mario_limoncie...@dell.com>
> Subject: Re: Dell XPS13: MCE (Hardware Error) reported
>
> On Fri, Jan 27, 2017 at 02:35:16PM +0100, Paul Menze
rio
> 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
>
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
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
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
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
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
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
Dear Ashosk, dear Borislav,
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
MCG status:
MCi status:
Dear Ashosk, dear Borislav,
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
MCG status:
MCi status:
Dear Boris,
On 01/09/17 12:05, Borislav Petkov wrote:
On Mon, Jan 09, 2017 at 11:55:41AM +0100, Paul Menzel wrote:
[…]
Also, is that just for MacBookPro11,3? The MCE for the Dell XPS13 looks
different from what I see, doesn’t it?
Yes, yours is different. I'm still waiting for you to
Dear Boris,
On 01/09/17 12:05, Borislav Petkov wrote:
On Mon, Jan 09, 2017 at 11:55:41AM +0100, Paul Menzel wrote:
[…]
Also, is that just for MacBookPro11,3? The MCE for the Dell XPS13 looks
different from what I see, doesn’t it?
Yes, yours is different. I'm still waiting for you to
On Mon, Jan 09, 2017 at 11:55:41AM +0100, Paul Menzel wrote:
> Do you mean *shouldn’t have been done*?
Yes.
> Should the discussion be referenced?
Yap, it will be.
> Also, is that just for MacBookPro11,3? The MCE for the Dell XPS13 looks
> different from what I see, doesn’t it?
Yes, yours is
On Mon, Jan 09, 2017 at 11:55:41AM +0100, Paul Menzel wrote:
> Do you mean *shouldn’t have been done*?
Yes.
> Should the discussion be referenced?
Yap, it will be.
> Also, is that just for MacBookPro11,3? The MCE for the Dell XPS13 looks
> different from what I see, doesn’t it?
Yes, yours is
On 01/06/17 17:54, Borislav Petkov wrote:
On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
Looks like we don't need a return value from therm_throt_process(),
we can fix that as void as well.
Right you are, here's v2:
---
From a8151fa6f18c2605eb7972061234f05e79b372c4 Mon Sep 17
On 01/06/17 17:54, Borislav Petkov wrote:
On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
Looks like we don't need a return value from therm_throt_process(),
we can fix that as void as well.
Right you are, here's v2:
---
From a8151fa6f18c2605eb7972061234f05e79b372c4 Mon Sep 17
Hi Boris
This looks good to me!
On Fri, Jan 06, 2017 at 05:54:23PM +0100, Borislav Petkov wrote:
> On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
> > Looks like we don't need a return value from therm_throt_process(),
> > we can fix that as void as well.
>
> Right you are, here's
Hi Boris
This looks good to me!
On Fri, Jan 06, 2017 at 05:54:23PM +0100, Borislav Petkov wrote:
> On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
> > Looks like we don't need a return value from therm_throt_process(),
> > we can fix that as void as well.
>
> Right you are, here's
On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
> Looks like we don't need a return value from therm_throt_process(),
> we can fix that as void as well.
Right you are, here's v2:
---
>From a8151fa6f18c2605eb7972061234f05e79b372c4 Mon Sep 17 00:00:00 2001
From: Borislav Petkov
On Fri, Jan 06, 2017 at 07:58:31AM -0800, Raj, Ashok wrote:
> Looks like we don't need a return value from therm_throt_process(),
> we can fix that as void as well.
Right you are, here's v2:
---
>From a8151fa6f18c2605eb7972061234f05e79b372c4 Mon Sep 17 00:00:00 2001
From: Borislav Petkov
Date:
Hi Boris
On Fri, Jan 06, 2017 at 12:16:17PM +0100, Borislav Petkov wrote:
> On Thu, Jan 05, 2017 at 05:26:17PM -0800, Raj, Ashok wrote:
> > Agree, since we have both a log and another agent to deal with it, it makes
> > no good reason to continue... Will pass this along, and have someone look at
Hi Boris
On Fri, Jan 06, 2017 at 12:16:17PM +0100, Borislav Petkov wrote:
> On Thu, Jan 05, 2017 at 05:26:17PM -0800, Raj, Ashok wrote:
> > Agree, since we have both a log and another agent to deal with it, it makes
> > no good reason to continue... Will pass this along, and have someone look at
On Thu, Jan 05, 2017 at 05:26:17PM -0800, Raj, Ashok wrote:
> Agree, since we have both a log and another agent to deal with it, it makes
> no good reason to continue... Will pass this along, and have someone look at
> cleaning this up.
Like this?
---
From: Borislav Petkov
Date:
On Thu, Jan 05, 2017 at 05:26:17PM -0800, Raj, Ashok wrote:
> Agree, since we have both a log and another agent to deal with it, it makes
> no good reason to continue... Will pass this along, and have someone look at
> cleaning this up.
Like this?
---
From: Borislav Petkov
Date: Fri, 6 Jan 2017
On Fri, Jan 06, 2017 at 12:56:11AM +0100, Borislav Petkov wrote:
> Oh, and it's not like the user can do anything - there's a thermald
> which is supposed to deal with all that. Which is not really
> trouble-free too, TBH. What happens if that thing dies? Fried CPU?
>
> So I say we should rip out
On Fri, Jan 06, 2017 at 12:56:11AM +0100, Borislav Petkov wrote:
> Oh, and it's not like the user can do anything - there's a thermald
> which is supposed to deal with all that. Which is not really
> trouble-free too, TBH. What happens if that thing dies? Fried CPU?
>
> So I say we should rip out
On Thu, Jan 05, 2017 at 03:28:00PM -0800, Raj, Ashok wrote:
> After looking at the code, seems like these events are logged as MCE's
> but are really picked from real lvt thermal event interrupts. via a fake
> bank 128 for MCE_THERMAL. These are not really HW MCE's, but fake ones
> created
>
On Thu, Jan 05, 2017 at 03:28:00PM -0800, Raj, Ashok wrote:
> After looking at the code, seems like these events are logged as MCE's
> but are really picked from real lvt thermal event interrupts. via a fake
> bank 128 for MCE_THERMAL. These are not really HW MCE's, but fake ones
> created
>
Hi Boris
On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
> On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> > Not sure if it is related, but I am also seeing those messages on my
> > MacBookPro11,3:
>
> Yours look to me like thermal throttling MCEs. And TBH
Hi Boris
On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
> On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> > Not sure if it is related, but I am also seeing those messages on my
> > MacBookPro11,3:
>
> Yours look to me like thermal throttling MCEs. And TBH
On Thu, Jan 05, 2017 at 09:03:10PM +, Pandruvada, Srinivas wrote:
> I suggest trying with the following kernel command line, if your
> getting notification to throttle from SMM before:
>
> intel_pstate=support_acpi_ppc
>
> opensuse doesn't start thermald by default.
>
Used the
On Thu, Jan 05, 2017 at 09:03:10PM +, Pandruvada, Srinivas wrote:
> I suggest trying with the following kernel command line, if your
> getting notification to throttle from SMM before:
>
> intel_pstate=support_acpi_ppc
>
> opensuse doesn't start thermald by default.
>
Used the
On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
>
> What does your /var/log/mcelog* log file contain?
>
There are no files there, but in the attached backtrace mcelog is mentioned
several times. Sorry I am not familiar with mcelog so I don't know where it
would be logging on
On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
>
> What does your /var/log/mcelog* log file contain?
>
There are no files there, but in the attached backtrace mcelog is mentioned
several times. Sorry I am not familiar with mcelog so I don't know where it
would be logging on
On Thu, 2017-01-05 at 12:43 -0800, Raj, Ashok wrote:
> Hi Boris
>
>
> On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
> >
> > On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> > >
> > > Not sure if it is related, but I am also seeing those messages on
> > >
On Thu, 2017-01-05 at 12:43 -0800, Raj, Ashok wrote:
> Hi Boris
>
>
> On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
> >
> > On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> > >
> > > Not sure if it is related, but I am also seeing those messages on
> > >
Hi Boris
On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
> On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> > Not sure if it is related, but I am also seeing those messages on my
> > MacBookPro11,3:
>
> Yours look to me like thermal throttling MCEs. And TBH
Hi Boris
On Thu, Jan 05, 2017 at 09:31:47PM +0100, Borislav Petkov wrote:
> On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> > Not sure if it is related, but I am also seeing those messages on my
> > MacBookPro11,3:
>
> Yours look to me like thermal throttling MCEs. And TBH
On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> Not sure if it is related, but I am also seeing those messages on my
> MacBookPro11,3:
Yours look to me like thermal throttling MCEs. And TBH we whould
not issue those as actual MCEs because they are not - they *signal*
On Thu, Jan 05, 2017 at 09:10:34PM +0100, Alexander Alemayhu wrote:
> Not sure if it is related, but I am also seeing those messages on my
> MacBookPro11,3:
Yours look to me like thermal throttling MCEs. And TBH we whould
not issue those as actual MCEs because they are not - they *signal*
On Thu, Jan 05, 2017 at 10:05:39PM +0800, Daniel J Blueman wrote:
>
> That said, I have seen this reoccur after boot; there were no other
> kernel messages around 300s uptime, and it hasn't occurred in the last
> hours since:
>
Not sure if it is related, but I am also seeing those messages on my
On Thu, Jan 05, 2017 at 10:05:39PM +0800, Daniel J Blueman wrote:
>
> That said, I have seen this reoccur after boot; there were no other
> kernel messages around 300s uptime, and it hasn't occurred in the last
> hours since:
>
Not sure if it is related, but I am also seeing those messages on my
On 5 January 2017 at 13:00, Daniel J Blueman wrote:
> On Thursday, January 5, 2017 at 9:20:04 AM UTC+8, Raj, Ashok wrote:
>> Hi Boris
>>
>> thanks for forwarding.
>>
>> > > CPUID Vendor Intel Family 6 Model 142
>> This is Kabylake Mobile
>>
>> > > Hardware event. This is not a
On 5 January 2017 at 13:00, Daniel J Blueman wrote:
> On Thursday, January 5, 2017 at 9:20:04 AM UTC+8, Raj, Ashok wrote:
>> Hi Boris
>>
>> thanks for forwarding.
>>
>> > > CPUID Vendor Intel Family 6 Model 142
>> This is Kabylake Mobile
>>
>> > > Hardware event. This is not a software error.
>>
On Thursday, January 5, 2017 at 9:20:04 AM UTC+8, Raj, Ashok wrote:
> Hi Boris
>
> thanks for forwarding.
>
> > > 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
On Thursday, January 5, 2017 at 9:20:04 AM UTC+8, Raj, Ashok wrote:
> Hi Boris
>
> thanks for forwarding.
>
> > > 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
Hi Boris
thanks for forwarding.
> > 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
> > MCG status:
> > MCi status:
> > Error
Hi Boris
thanks for forwarding.
> > 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
> > MCG status:
> > MCi status:
> > Error
Lemme add some more folks to CC.
On Wed, Jan 04, 2017 at 04:42:18PM +0100, Paul Menzel wrote:
> Dear Linux folks,
>
>
> The logs contain the following messages.
>
> From Linux 4.10-rc2+ (0f64df301240 Merge branch 'parisc-4.10-2' of
>
Lemme add some more folks to CC.
On Wed, Jan 04, 2017 at 04:42:18PM +0100, Paul Menzel wrote:
> Dear Linux folks,
>
>
> The logs contain the following messages.
>
> From Linux 4.10-rc2+ (0f64df301240 Merge branch 'parisc-4.10-2' of
>
Dear Linux folks,
The logs contain the following messages.
From Linux 4.10-rc2+ (0f64df301240 Merge branch 'parisc-4.10-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux):
Jan 04 16:17:51 xps13 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0
Bank 6:
Dear Linux folks,
The logs contain the following messages.
From Linux 4.10-rc2+ (0f64df301240 Merge branch 'parisc-4.10-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux):
Jan 04 16:17:51 xps13 kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0
Bank 6:
60 matches
Mail list logo