From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
Michael Karcher <Michael.Karcher@fu-berlin.de>,
linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: power management regression in linux 3.10?
Date: Tue, 4 Jun 2013 16:19:54 +0200 [thread overview]
Message-ID: <20130604141952.GI14973@somewhere> (raw)
In-Reply-To: <2330824.Xqf4iUAbIP@vostro.rjw.lan>
On Mon, Jun 03, 2013 at 10:04:30PM +0200, Rafael J. Wysocki wrote:
> On Monday, June 03, 2013 12:37:21 PM Dirk Brandewie wrote:
> > On 06/03/2013 12:34 PM, Rafael J. Wysocki wrote:
> > > On Monday, June 03, 2013 07:56:15 PM Michael Karcher wrote:
> > >> Hello,
> > >>
> > >> I am using an IBM ThinkPad T60 (i915, Core 2 Duo T7200) and recently
> > >> upgraded from a custom 3.7 kernel to a custom 3.10-rc4 kernel
> > >> (v3.10-rc4-1-gc026d8e).
> > >> After upgrading, I get around 17-20W power usage instead of 12-15W power
> > >> usage as I had with 3.7. powertop show that CPU0 is in state POLL all of
> > >> the idle time, while CPU1 correctly enters C3.
With CONFIG_NO_HZ_FULL it is expected that CPU 0 consumes more power because
it handles the timekeeping for every other CPUs and so it never stop its tick.
Paul McKenney is working on a solution to solve that.
But if you see something similar on the other CPUs it's a bug.
Thanks.
next prev parent reply other threads:[~2013-06-04 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 17:56 power management regression in linux 3.10? Michael Karcher
2013-06-03 19:34 ` Rafael J. Wysocki
2013-06-03 19:37 ` Dirk Brandewie
2013-06-03 20:04 ` Rafael J. Wysocki
2013-06-04 14:19 ` Frederic Weisbecker [this message]
2013-06-04 1:08 ` Michael Karcher
2013-06-04 11:30 ` power management regression in linux 3.10? (related to CONFIG_NO_HZ_FULL) Rafael J. Wysocki
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=20130604141952.GI14973@somewhere \
--to=fweisbec@gmail.com \
--cc=Michael.Karcher@fu-berlin.de \
--cc=dirk.brandewie@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-pm@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