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 1PY6dQ-0005u6-KB for garchives@archives.gentoo.org; Thu, 30 Dec 2010 00:44:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 166A3E055E; Thu, 30 Dec 2010 00:43:27 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id A7657E055E for ; Thu, 30 Dec 2010 00:43:26 +0000 (UTC) Received: by wwi18 with SMTP id 18so10604353wwi.10 for ; Wed, 29 Dec 2010 16:43:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=8qUDkEdj55kQKIbcsi5zZvfsQuciHLjbhnRQpcj3SWU=; b=qWb4lNpONJ7T4HRHIovaNG5BoZJGBq+JMBhRE2NtFTOOBwydA6C2qiw2rkp2J4Lcid HjjJMiON1AK2lsxVtQAjIA4i+uAhouKijHTga/DtmXi134MI6pjh++Ew1kNXl5LZh6wn n83cvL4idaKKeuaqxG6iXtfCi/Ihj7aQjcFW4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=kYkM8L7VjR4E9XnN9bKMQ1r6ID37t9+b/miDq55j1l6obLTUD7+FCMP1IYbES2lor8 32I1K7y8mfOr8xpxDell71u7Y4VjGJ4w/nol+VsTEMixTKJSlJjvHZJrWfzl3CdPRNp2 jyXsJIf/NFLMSQOM4uQRR0N7EjkGpzA8jJo8s= Received: by 10.216.172.212 with SMTP id t62mr15945464wel.60.1293669805527; Wed, 29 Dec 2010 16:43:25 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id e12sm7429384wer.12.2010.12.29.16.43.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 29 Dec 2010 16:43:24 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Core i7 M620 power management problem Date: Thu, 30 Dec 2010 00:43:18 +0000 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r5; KDE/4.4.5; x86_64; ; ) References: In-Reply-To: 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 Content-Type: multipart/signed; boundary="nextPart41745699.qgFr4sxiab"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201012300043.29899.michaelkintzios@gmail.com> X-Archives-Salt: 426f6423-7d65-448c-a243-7944a79fb490 X-Archives-Hash: 74d61fda186a4fb6cb54b6a8fd08ead7 --nextPart41745699.qgFr4sxiab Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Wednesday 29 December 2010 20:51:05 Bill Longman wrote: > > 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. >=20 > Here's an interesting item: >=20 > 12:41:00# cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit > 1199000 >=20 > 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) >=20 > So, why are there micro-spikes of higher frequencies in the above stats? > The stats section says there are only five transitions. Just a wild guess: are you running some desktop applet that manages the cp= u=20 frequency and is stuck on manual with a low setting? I have the i7 Q 720 @ 1.60GHz, which is supposedly go up to 2.8G with turbo= =20 boost, but can't say that I have ever seen it going that high ... not sure = if=20 there's a setting somewhere I should tweak. This is from cpuinfo: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz stepping : 5 cpu MHz : 931.000 cache size : 6144 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov=20 pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp= lm=20 constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmper= f=20 pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_= 2=20 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid bogomips : 3192.42 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D As you can see power management is also blank. These are my frequencies: $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_* 1597000 1596000 1463000 1330000 1197000 1064000 931000=20 conservative userspace powersave ondemand performance=20 931000 acpi-cpufreq ondemand 1597000 931000 PS. Any ideas what makes that turbo thingy kick in? =2D-=20 Regards, Mick --nextPart41745699.qgFr4sxiab Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAk0b1bEACgkQVTDTR3kpaLajTwCeKS87J+kx6lJPJQI0N/t75mOm BNMAoPqi1cOGhDZAUhBPabcZPLBVLwt8 =ukGv -----END PGP SIGNATURE----- --nextPart41745699.qgFr4sxiab--