From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Chen Gong <gong.chen@linux.intel.com>
Cc: "R, Durgadoss" <durgadoss.r@intel.com>,
"linux-x86_64@vger.kernel.org" <linux-x86_64@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CPU clock throttled prints..
Date: Thu, 12 Jan 2012 06:46:43 -0800 [thread overview]
Message-ID: <4F0EF253.7050308@gmail.com> (raw)
In-Reply-To: <4F0E4147.7000903@linux.intel.com>
On 01/11/2012 06:11 PM, Chen Gong wrote:
> 于 2011/7/5 13:36, R, Durgadoss 写道:
>> Hi All,
>>
>> I am getting these prints in my Atom based device, running 2.6.35 kernel.
>>
>> [ 350.084005] CPU0: Temperature above threshold, cpu clock throttled
>> (total
>> events = 26)
>> [ 350.084029] CPU1: Temperature above threshold, cpu clock throttled
>> (total
>> events = 26)
>> [ 350.085293] CPU0: Temperature/speed normal
>> [ 350.085311] CPU1: Temperature/speed normal
>>
>> Seems like these are from therm_throt.c and the flow for this,
>> Starts from smp_thermal_interrupt(...) method.
>>
>> Can somebody tell me when this method gets called ?
>> Also, does this actually throttle the CPU ?
>>
>
> try to apply this patch 29e9bf1841e4f (x86, mce, therm_throt: Don't report
> power limit and package level thermal throttle events in mcelog)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-x86_64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
probably not the best solution, but I just ended up disabling the
function in the kernel: (either its below or its under a different name)
X86_MCE_INTEL = n
this way when I watch hulu, dmesg is not spammed with something about
"above threshold" by just watching a movie.
Justin P. Mattock
prev parent reply other threads:[~2012-01-12 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 5:36 CPU clock throttled prints R, Durgadoss
2012-01-12 2:11 ` Chen Gong
2012-01-12 14:46 ` Justin P. Mattock [this message]
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=4F0EF253.7050308@gmail.com \
--to=justinmattock@gmail.com \
--cc=durgadoss.r@intel.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox