From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Flamm Subject: Re: I haven't been able to set the chosen policy for CPU0 Date: Mon, 19 May 2008 19:18:25 +0200 Message-ID: <200805191918.25944.alcc@gmx.de> References: <200805191842.22216.alcc@gmx.de> <924EFEDD5F540B4284297C4DC59F3DEE01119E0B@orsmsx423.amr.corp.intel.com> Reply-To: alcc@gmx.de Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEE01119E0B@orsmsx423.amr.corp.intel.com> Content-Disposition: inline List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: cpufreq-bounces@lists.linux.org.uk Errors-To: cpufreq-bounces+glkc-cpufreq=m.gmane.org+glkc-cpufreq=m.gmane.org@lists.linux.org.uk To: cpufreq@lists.linux.org.uk >>I think I can now reproduce that misbehaviour. I happens when >>both of my cores >>are at 100% =A0- than min- *and* max-frequency fall down to >>minimum (1000000Hz) > Looks like the CPUs are being driver to lower freq due to temperature > limits. CPUs being busy is increasing the temp and they go to lower freq > until they reach the lower temp. Looking at > /proc/acpi/thermal_zone/*/* > when this happens can confirm this. First of all, thx for the reply. = Before, at, and after the freqency falls doen to minimum: $ cat /proc/acpi/thermal_zone/THM0/state state: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ok So its something else. Regards, Christian.