public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-acpi@vger.kernel.org
Subject: Re: 2.6.25 regression: powertop says 120K wakeups/sec
Date: Sat, 22 Mar 2008 17:35:00 -0700	[thread overview]
Message-ID: <20080322173500.7b8b6751.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080322202454.9D69DCC0EF@adsl-69-226-248-13.dsl.pltn13.pacbell.net>

On Sat, 22 Mar 2008 13:24:54 -0700 David Brownell <david-b@pacbell.net> wrote:

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

This is likely to be an acpi regression, isn't it?

A git-bisect would be nice, please.

       reply	other threads:[~2008-03-23  0:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080322202454.9D69DCC0EF@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
2008-03-23  0:35 ` Andrew Morton [this message]
2008-03-23 18:04   ` 2.6.25 regression: powertop says 120K wakeups/sec Alexey Starikovskiy
2008-03-28 19:01   ` David Brownell
2008-03-28 19:13     ` Pallipadi, Venkatesh
2008-03-28 19:44       ` David Brownell
2008-03-28 20:30         ` Venki Pallipadi
2008-03-28 21:09           ` David Brownell
2008-03-28 21:55             ` Pallipadi, Venkatesh
2008-03-28 22:09               ` David Brownell
2008-03-28 22:56                 ` Venki Pallipadi
2008-03-28 23:01                   ` Rafael J. Wysocki
2008-03-28 23:07                     ` Pallipadi, Venkatesh
2008-03-31 17:42                     ` Mark Lord
2008-03-31 18:34                       ` Pallipadi, Venkatesh
2008-03-28 23:36                   ` David Brownell
2008-03-28 23:51                     ` Pallipadi, Venkatesh
2008-03-29  0:15                       ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080322173500.7b8b6751.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox