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 1PYM3S-0002ci-7X for garchives@archives.gentoo.org; Thu, 30 Dec 2010 17:12:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EFA3FE059B; Thu, 30 Dec 2010 17:11:04 +0000 (UTC) Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.212.181]) by pigeon.gentoo.org (Postfix) with ESMTP id AE498E059B for ; Thu, 30 Dec 2010 17:11:04 +0000 (UTC) Received: by pxi2 with SMTP id 2so3106852pxi.40 for ; Thu, 30 Dec 2010 09:11:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=31HKAmZyKNT9t1l0FQfSWBCl3FqnYYyEt9Xd+rRMJg8=; b=s9Fg1V2tJFNPRBOXnrQ0coP0Tw4fPJS/xl30hZdVlndwmr6rtLPt1eTWIYdzbxrDYW uemKbb8FecMEAJH80ABHYKq6rblK3h3Z1w719/FtRIeMegGsGSAd1q8QZulLPAIsDl2n mRuNtvMk+b9rdoOAxghWRkTHAzaZNDkvlHIgA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=aGbTdDzucC3qjiJarQ+Zp2G95aEx4opOZ7O5PaB9Atkx3GoE4m5DrTuVv9QAveLJMF Ul+WuNcBvsOpYvBYzyzwbTFVwOZulSncFyeCkzXZUOf7rlm0+4AL9RTNxSUYEfye/B+D eR7y4WDSeX6jXUHCEqOjLdVny04S+bHZ/i5K8= Received: by 10.143.3.6 with SMTP id f6mr13384158wfi.205.1293729063694; Thu, 30 Dec 2010 09:11:03 -0800 (PST) Received: from [198.186.240.124] (ip18.83.dhcp-acs2.pdx.iinet.com [198.145.83.18]) by mx.google.com with ESMTPS id v19sm22716114wfh.0.2010.12.30.09.11.02 (version=SSLv3 cipher=RC4-MD5); Thu, 30 Dec 2010 09:11:02 -0800 (PST) Message-ID: <4D1CBD21.3080607@gmail.com> Date: Thu, 30 Dec 2010 09:10:57 -0800 From: Bill Longman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101229 Lightning/1.0b3pre Thunderbird/3.1.7 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Core i7 M620 power management problem References: <201012300043.29899.michaelkintzios@gmail.com> <201012300821.24965.michaelkintzios@gmail.com> In-Reply-To: <201012300821.24965.michaelkintzios@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: ea2861e2-20e5-471e-a21c-d488199c7a5d X-Archives-Hash: 6f6de04e760c10f7651b7d7200c08385 On 12/30/2010 12:21 AM, Mick wrote: > On Thursday 30 December 2010 03:16:05 Bill Longman wrote: > > This is what my i7 Q is showing: > > Handle 0x0005, DMI type 4, 42 bytes > Processor Information > Socket Designation: U2E1 > Type: Central Processor > Family: > Manufacturer: Intel > ID: E5 06 01 00 FF FB EB BF > Version: CPU Version > Voltage: 3.3 V > External Clock: 133 MHz > Max Speed: 4096 MHz <--my max speed with turbo should be 2.8GHz?--> > Current Speed: 1600 MHz <--my max speed without turbo--> > Status: Populated, Enabled > Upgrade: ZIF Socket > L1 Cache Handle: 0x0006 > L2 Cache Handle: 0x0007 > L3 Cache Handle: 0x0008 > Serial Number: Not Specified > Asset Tag: Not Specified > Part Number: Not Specified > Core Count: 4 > Core Enabled: 4 > Thread Count: 8 > Characteristics: > 64-bit capable > > My turbo reading leads me to think that the dmidecode is not necessarily > reporting what the CPU can do. I've always laughed at the shoddy workmanship of DMI. I don't know the percentage of boards with "To Be Filled By O.E.M." in them, but most of it is useful information. Here's another snapshot of idle stats, so it looks like it's handling the idle routines okay: /sys/devices/system/cpu/cpu0/cpuidle 09:05:05# for a in {0..3}; do echo === state$a ===; ls state$a;cat state$a/*; done === state0 === desc latency name power time usage CPUIDLE CORE POLL IDLE 0 C0 4294967295 24712609 9234 === state1 === desc latency name power time usage MWAIT 0x00 3 NHM-C1 4294967294 530943161 2079744 === state2 === desc latency name power time usage MWAIT 0x10 20 NHM-C3 4294967293 4419507305 4950330 === state3 === desc latency name power time usage MWAIT 0x20 200 NHM-C6 4294967292 49546556808 7879505 It still points to that "max cpu freq" as the culprit. I don't recall what kicks in the turbo mode on the i7's. I thought it was simply bumping the speed of one core if it could keep the other core(s) in the deep sleep state. So, a single threaded process would get a speed improvement. If your other cores were running you'd be out of luck. Could be wrong. Brain's been running about half a century now, so it's wearing out.