From: Johannes Berg <johannes@sipsolutions.net>
To: Dave Jones <davej@redhat.com>
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 18:35:43 +0100 [thread overview]
Message-ID: <1197480944.6558.132.camel@johannes.berg> (raw)
In-Reply-To: <20071212173001.GA18973@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Hi,
> 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)
Hah ok, but it's still odd that it changes to a different one.
> 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?
Sure. I'll do it tonight and send it tomorrow.
> Also, does /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
> have performance in *all* the cpus?
My four CPUs can only change together so I don't think that is relevant.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2007-12-12 17:36 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
2007-12-12 17:35 ` Johannes Berg [this message]
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=1197480944.6558.132.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--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).