From: Andi Kleen <ak@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold, cpu_clock_throttled(total_events=#)
Date: Fri, 04 Dec 2015 10:25:55 -0800 [thread overview]
Message-ID: <20151204182555.GE18534@tassilo.jf.intel.com> (raw)
In-Reply-To: <87vb8fqaag.fsf@yhuang-dev.intel.com>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
> 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)
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
linux-edac <linux-edac@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [lkp] [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#)
Date: Fri, 4 Dec 2015 10:25:55 -0800 [thread overview]
Message-ID: <20151204182555.GE18534@tassilo.jf.intel.com> (raw)
In-Reply-To: <87vb8fqaag.fsf@yhuang-dev.intel.com>
> 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)
next prev parent reply other threads:[~2015-12-04 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 1:20 [x86/mce] 81ffdcdd97: kmsg.CPU61:Package_temperature_above_threshold, cpu_clock_throttled(total_events=#) kernel test robot
2015-12-04 10:48 ` Borislav Petkov
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 message]
2015-12-04 18:25 ` Andi Kleen
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=20151204182555.GE18534@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=lkp@lists.01.org \
/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.