[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20151204182555.GE18534@tassilo.jf.intel.com>
Date: Fri, 4 Dec 2015 10:25:55 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: kernel test robot <ying.huang@...ux.intel.com>
Cc: lkp@...org, LKML <linux-kernel@...r.kernel.org>,
linux-edac <linux-edac@...r.kernel.org>,
Tony Luck <tony.luck@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...e.de>, Ingo Molnar <mingo@...nel.org>
Subject: Re: [lkp] [x86/mce] 81ffdcdd97:
kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#)
> 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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists