DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Date:From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-Id;
  b=wfCNgUKoSgn8xfKZVo+m952oIE6Py7xm25jIPEHtt1qyfGVXcslCqNLuTwt/Zq6aVR0W96xr73S0PvLsVjYX4N2KCsJ6Lh0XcswAGwAHonZrl6eUbkQzztI9YiJ8QefVKnunRFRWtUYzNc9meJJ4Sk8LzZABW5KbrhspBCn1QZA=  ;
Date: Sat, 22 Mar 2008 13:24:54 -0700
From: David Brownell <david-b@pacbell.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.25 regression: powertop says 120K wakeups/sec
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20080322202454.9D69DCC0EF@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1059
Lines: 25

I noticed this with 2.6.25-rc2 (if not before), and the problem
is still there with 2.6.25-rc6-git (as of this AM).

System is an Athlon64 single CPU laptop, and instead of reading a
few dozen wakeups per second, it says a many tens of thousands...
clearly wrong.  In previous kernels it gave more plausible counts;
unfortunately high because of various un-evolved desktop tools in
this Ubuntu system (Feisty).

Possibly more truthful, it says that the system never enters
C1 or C2, and spends all its time in C0.  Though if I look at
/sys/devices/system/cpu/cpu0/cpuidle/state[01]/usage, that
seems to tell a different story ... it's C0 that's never used.
In previous kernels it reported time in both C0 and C2.  ISTR
some patch to avoid C2, which would explain part of this.

Comments or fixes, anyone?

- Dave

--
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/