From: Michael Karcher <Michael.Karcher@fu-berlin.de>
To: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: power management regression in linux 3.10?
Date: Tue, 04 Jun 2013 03:08:48 +0200 [thread overview]
Message-ID: <1370308128.6305.3.camel@localhost> (raw)
In-Reply-To: <51ACF071.702@gmail.com>
Am Montag, den 03.06.2013, 12:37 -0700 schrieb Dirk Brandewie:
> On 06/03/2013 12:34 PM, Rafael J. Wysocki wrote:
> > On Monday, June 03, 2013 07:56:15 PM Michael Karcher wrote:
> >> Hello,
> > Yes, please try with CONFIG_NO_HZ_IDLE and see if you can reproduce the
> > problem.
Instead of doing that, I successfully applied Dirk's suggestion. Is
CONFIG_NO_HZ + CONFIG_NO_HZ_IDLE worth testing?
> > Does your system use intel_idle? You've set that in .config, but can you check
> > what dmesg says, please?
No, intel_idle complains it doesn't support my CPU family.
> Unset CONFIG_NO_HZ it is setting CONFIG_CPU_IDLE_GOV_MENU which with
> CONFIG_NO_HZ_FULL set is confusing intel_pstate. I am still trying to
> figure out what the root cause is commit 5811d996 seems to be implicated.
Unsetting CONFIG_NO_HZ helped. Now CPU0 is using C states again.
> --Dirk
Regards,
Michael Karcher
next prev parent reply other threads:[~2013-06-03 23:08 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
2013-06-04 1:08 ` Michael Karcher [this message]
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=1370308128.6305.3.camel@localhost \
--to=michael.karcher@fu-berlin.de \
--cc=dirk.brandewie@gmail.com \
--cc=fweisbec@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