public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: [lkp] [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#)
       [not found] <87vb8fqaag.fsf@yhuang-dev.intel.com>
@ 2015-12-04 10:48 ` Borislav Petkov
  2015-12-04 18:25 ` Andi Kleen
  1 sibling, 0 replies; 2+ messages in thread
From: Borislav Petkov @ 2015-12-04 10:48 UTC (permalink / raw)
  To: kernel test robot, Tony Luck
  Cc: Andi Kleen, lkp, LKML, linux-edac, Tony Luck, Peter Zijlstra,
	Linus Torvalds, H. Peter Anvin, Thomas Gleixner, Ingo Molnar

On Fri, Dec 04, 2015 at 09:20:39AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 81ffdcdd97d94110627caa81c23d5d780083731d ("x86/mce: Fix thermal throttling reporting after kexec")
> 
> This may be the intended behavior, just FYI.

Should be...

Let me get this straight - before this commit, the messages don't
appear, yes?

Looking at the hunk and AFAICT, it checks APIC_LVTTHMR[VEC] and it did
bail out if something was there != 0 before.

With this check removed, we go and actually init.

So I can imagine BIOS programming stuff in it already and us not even
initializing thermal throttling due to that. And this commit actually
*fixed* it on baremetal too.

But that would be crazy, BIOS would never do something like that?!</sarcasm>

Tony?

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [lkp] [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#)
       [not found] <87vb8fqaag.fsf@yhuang-dev.intel.com>
  2015-12-04 10:48 ` [lkp] [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#) Borislav Petkov
@ 2015-12-04 18:25 ` Andi Kleen
  1 sibling, 0 replies; 2+ messages in thread
From: Andi Kleen @ 2015-12-04 18:25 UTC (permalink / raw)
  To: kernel test robot
  Cc: lkp, LKML, linux-edac, Tony Luck, Peter Zijlstra, Linus Torvalds,
	H. Peter Anvin, Thomas Gleixner, Borislav Petkov, Ingo Molnar

> commit 81ffdcdd97d94110627caa81c23d5d780083731d ("x86/mce: Fix thermal throttling reporting after kexec")
> 
> This may be the intended behavior, just FYI.

Yes, it's intended. Your system is overheating, and I assume 0day uses kexec.
Previously you completely missed these messages because they were disabled
after the first kexec. So now they are correctly reported.

-Andi

> 
> [  228.096596] CPU47: Core temperature above threshold, cpu clock throttled (total events = 1)
> [  228.096597] CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
> [  228.096599] CPU19: Package temperature above threshold, cpu clock throttled (total events = 1)
> [  228.096601] CPU9: Package temperature above threshold, cpu clock throttled (total events = 1)
> [  228.096603] CPU53: Package temperature above threshold, cpu clock throttled (total events = 1)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-12-04 18:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <87vb8fqaag.fsf@yhuang-dev.intel.com>
2015-12-04 10:48 ` [lkp] [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#) Borislav Petkov
2015-12-04 18:25 ` Andi Kleen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox