From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PY31a-0002vl-6X for garchives@archives.gentoo.org; Wed, 29 Dec 2010 20:53:34 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 281F0E063D; Wed, 29 Dec 2010 20:51:06 +0000 (UTC) Received: from mail-iw0-f181.google.com (mail-iw0-f181.google.com [209.85.214.181]) by pigeon.gentoo.org (Postfix) with ESMTP id E71CEE063D for ; Wed, 29 Dec 2010 20:51:05 +0000 (UTC) Received: by iwn3 with SMTP id 3so14692205iwn.40 for ; Wed, 29 Dec 2010 12:51:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=ls4eYx1zhnAwMf7suTor2SxjfJdbaYjei4dEOf7I4Ho=; b=xU59zt1zELbjVSn0tmaS71I4zXoHqUutHhqE/nbZFxoucXdH4ybSJNzmmmwGkME8oD Rj+dPZnquS8om7H6MWlIDlmRydRw+j7M3jaO6S1DGW3mtX3I9Oov5TNZiNuTf1ExdUX/ i+c8PYyxAzyXsWM/y5vU1O1JJeucy5THImpTE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tvoMXJJKCr5psnEulWlmD7y6Unv/I1pMgil1niRHlbz5zuormLTrmkSa5ocrHHYuyK HiqnXAn6Z8qhnYRVCWD3+0zSgNZ+exY9TSwWhYjeb2C+/KzZobEOn4BmmjfWav0Wctmr FkQRCIzhGe7NPm5UZCumpKWG4q97Y3gqQw89Q= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.231.11.72 with SMTP id s8mr15351627ibs.40.1293655865468; Wed, 29 Dec 2010 12:51:05 -0800 (PST) Received: by 10.231.161.195 with HTTP; Wed, 29 Dec 2010 12:51:05 -0800 (PST) In-Reply-To: References: <4D1B7F7B.3070903@xunil.at> <4D1B9238.70707@xunil.at> Date: Wed, 29 Dec 2010 12:51:05 -0800 Message-ID: Subject: Re: [gentoo-user] Core i7 M620 power management problem From: Bill Longman To: lists@xunil.at, gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0003255753da52a967049892ba3f X-Archives-Salt: 366b2b2a-7ef1-4365-a6c8-a37d9e2524a3 X-Archives-Hash: a42254d864232d227c7c2bd8fb38f258 --0003255753da52a967049892ba3f Content-Type: text/plain; charset=UTF-8 > > Yeah, the cpufreq utils show all the relevant information. I use the > acpi-cpufreq driver and when I didn't use it nothing happened. cpufreq-aperf > shows each CPU at 1.2GHz. I'll look at the EIST in BIOS, too. Thanks for the > pointers. > Here's an interesting item: 12:41:00# cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit 1199000 which sort of jives with the "asserted by call to hardware" in the cpufreq-info section: analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.67 GHz available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 1.20 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 1.20 GHz (asserted by call to hardware). cpufreq stats: 2.67 GHz:0.25%, 2.67 GHz:0.01%, 2.53 GHz:0.01%, 2.40 GHz:0.01%, 2.27 GHz:0.01%, 2.13 GHz:0.01%, 2.00 GHz:0.01%, 1.87 GHz:0.01%, 1.73 GHz:0.01%, 1.60 GHz:0.01%, 1.47 GHz:0.01%, 1.33 GHz:0.01%, 1.20 GHz:99.61% (28) So, why are there micro-spikes of higher frequencies in the above stats? The stats section says there are only five transitions. -- Bill Longman --0003255753da52a967049892ba3f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yeah, the cpufreq= utils show all the relevant information. I use the acpi-cpufreq driver and= when I didn't use it nothing happened. cpufreq-aperf shows each CPU at= 1.2GHz. I'll look at the EIST in BIOS, too. Thanks for the pointers.

Here's an interesting item:

12:41:00# cat /sys/= devices/system/cpu/cpu0/cpufreq/bios_limit
1199000

which sort of = jives with the "asserted by call to hardware" in the cpufreq-info= section:
analyzing CPU 3:
=C2=A0 driver: acpi-cpufreq
=C2=A0 CPUs which run at= the same hardware frequency: 0 1 2 3
=C2=A0 CPUs which need to have the= ir frequency coordinated by software: 3
=C2=A0 maximum transition latenc= y: 10.0 us.
=C2=A0 hardware limits: 1.20 GHz - 2.67 GHz
=C2=A0 available frequency steps: 2.67 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2= .27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 G= Hz, 1.20 GHz
=C2=A0 available cpufreq governors: conservative, ondemand,= userspace, powersave, performance
=C2=A0 current policy: frequency should be within 1.20 GHz and 1.20 GHz.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The governor "performance" may dec= ide which speed to use
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 within this range.=C2=A0 current CPU frequency is 1.20 GHz (asserted by call to hardware).<= br> =C2=A0 cpufreq stats: 2.67 GHz:0.25%, 2.67 GHz:0.01%, 2.53 GHz:0.01%, 2.40 = GHz:0.01%, 2.27 GHz:0.01%, 2.13 GHz:0.01%, 2.00 GHz:0.01%, 1.87 GHz:0.01%, = 1.73 GHz:0.01%, 1.60 GHz:0.01%, 1.47 GHz:0.01%, 1.33 GHz:0.01%, 1.20 GHz:99= .61%=C2=A0 (28)

So, why are there micro-spikes of higher frequencies in the above stats= ? The stats section says there are only five transitions.


--
Bill Longman
--0003255753da52a967049892ba3f--