linux-kernel - Re: CPU clock throttled prints..

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Jan 2012 10:11:19 +0800
From:	Chen Gong <gong.chen@...ux.intel.com>
To:	"R, Durgadoss" <durgadoss.r@...el.com>
CC:	"linux-x86_64@...r.kernel.org" <linux-x86_64@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: CPU clock throttled prints..

于 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-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/