Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758323AbYC1V62 (ORCPT ); Fri, 28 Mar 2008 17:58:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756516AbYC1V6S (ORCPT ); Fri, 28 Mar 2008 17:58:18 -0400 Received: from mga11.intel.com ([192.55.52.93]:20226 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756189AbYC1V6R convert rfc822-to-8bit (ORCPT ); Fri, 28 Mar 2008 17:58:17 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.25,572,1199692800"; d="scan'208";a="541879182" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Subject: RE: 2.6.25 regression: powertop says 120K wakeups/sec Date: Fri, 28 Mar 2008 14:55:57 -0700 Message-ID: <924EFEDD5F540B4284297C4DC59F3DEEC83E08@orsmsx423.amr.corp.intel.com> In-Reply-To: <200803281409.09622.david-b@pacbell.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 2.6.25 regression: powertop says 120K wakeups/sec Thread-Index: AciRGnC/0WCq1ZaaQ6ix0UXSJEIPPQAAajwA References: <20080322202454.9D69DCC0EF@adsl-69-226-248-13.dsl.pltn13.pacbell.net> <200803281244.27012.david-b@pacbell.net> <20080328203014.GA16105@linux-os.sc.intel.com> <200803281409.09622.david-b@pacbell.net> From: "Pallipadi, Venkatesh" To: "David Brownell" Cc: "Andrew Morton" , , "Rafael J. Wysocki" , , "Len Brown" X-OriginalArrivalTime: 28 Mar 2008 21:53:54.0550 (UTC) FILETIME=[3774B160:01C8911E] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2116 Lines: 53 >-----Original Message----- >From: David Brownell [mailto:david-b@pacbell.net] >Sent: Friday, March 28, 2008 2:09 PM >To: Pallipadi, Venkatesh >Cc: Andrew Morton; linux-kernel@vger.kernel.org; Rafael J. >Wysocki; linux-acpi@vger.kernel.org; Len Brown >Subject: Re: 2.6.25 regression: powertop says 120K wakeups/sec > >On Friday 28 March 2008, Venki Pallipadi wrote: >> Can you send me the output of >> # grep . /sys/devices/system/cpu/cpu*/cpuidle/*/* >> with upstream kernel. > >This is "upstream" to 3085354de635179d70c240e6d942bcbd1d93056c: > >/sys/devices/system/cpu/cpu0/cpuidle/state0/desc:CPUIDLE CORE POLL IDLE >/sys/devices/system/cpu/cpu0/cpuidle/state0/latency:0 >/sys/devices/system/cpu/cpu0/cpuidle/state0/name:C0 >/sys/devices/system/cpu/cpu0/cpuidle/state0/power:4294967295 >/sys/devices/system/cpu/cpu0/cpuidle/state0/time:0 >/sys/devices/system/cpu/cpu0/cpuidle/state0/usage:0 >/sys/devices/system/cpu/cpu0/cpuidle/state1/desc: >/sys/devices/system/cpu/cpu0/cpuidle/state1/latency:0 >/sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1 >/sys/devices/system/cpu/cpu0/cpuidle/state1/power:0 >/sys/devices/system/cpu/cpu0/cpuidle/state1/time:2781727265 >/sys/devices/system/cpu/cpu0/cpuidle/state1/usage:927242422 > >... as I mentioned, powertop says C2 doesn't get used any more, >moreover that only C0 ever gets used. The "usage" seems to be >saying otherwise. > Looks like C2 state detection got broken somehow.. There was new state0 (polling) that was added recently which should never get used. state1 is actually C1 which for some reason is not staying idle and waking up immediately (that is the reason for high usage). And C2 is missing. I do see, in acpidump that you sent, there is a C2 state info there. You should have a dmesg line which looks like ACPI: CPU0 (power states: C1[C1] C2[C2] Do you see C2 in such line? Thanks, Venki -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/