linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	linux-pm <linux-pm@lists.linux-foundation.org>,
	cpufreq <cpufreq@lists.linux.org.uk>
Subject: Re: cpu frequency governor regression (?)
Date: Wed, 12 Dec 2007 12:30:01 -0500	[thread overview]
Message-ID: <20071212173001.GA18973@redhat.com> (raw)
In-Reply-To: <1197399165.2214.15.camel@johannes.berg>

On Tue, Dec 11, 2007 at 07:52:45PM +0100, Johannes Berg wrote:
 > Hi,
 > 
 > No idea who to bother with this and maybe it's just a
 > misconfiguration... Apologies if my guesses are totally wrong.
 > 
 > I'm currently on 2.6.24-rc3 (+wireless-2.6#everything) but couldn't find
 > any patches between that and 2.6.24-rc5 that seemed relevant.
 > 
 > On my quad powermac, I'm seeing the cpufreq governor changed by a
 > hibernation cycle. My default governor is "userspace", which is driven
 > by powernowd (because the latency is too high "ondemand" doesn't like my
 > machine) but after a hibernation cycle I'm having the governor set to
 > "performance".

bizarre. It should default back to whatever CONFIG_CPU_FREQ_DEFAULT_* option
was set.  (Arguably a bug in itself, as we don't track & restore them
on resume, so if you changed from the default after booting: splat)

Why you're getting the performance governor is puzzling though.
Can you enable CONFIG_CPU_FREQ_DEBUG=y, and boot with cpufreq.debug=7
and send the log from a transition across hibernate?

Also, does /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor 
have performance in *all* the cpus?

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-12-12 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 18:52 cpu frequency governor regression (?) Johannes Berg
2007-12-12 17:30 ` Dave Jones [this message]
2007-12-12 17:35   ` Johannes Berg
2007-12-12 19:53   ` Johannes Berg

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=20071212173001.GA18973@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).