From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 8671] New: CPU frequency always on highest frequency after wakeup from suspend to disk
Date: Mon, 25 Jun 2007 04:57:33 -0700 (PDT) [thread overview]
Message-ID: <bug-8671-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=8671
Summary: CPU frequency always on highest frequency after wakeup
from suspend to disk
Product: Power Management
Version: 2.5
KernelVersion: 2.6.22-rc5-git8
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: linux@markus-schaub.de
Most recent kernel where this bug did not occur: unkown
Distribution: Gentoo Linux
Hardware Environment: IBM Thinkpad T43
Software Environment:
Problem Description: cpufreq_conservative doesn't scale CPU frequency anymore
after wakeup from suspend to disk, instead CPU runs always with the highest
available frequency. Scaling driver is acpi-cpufreq.
Steps to reproduce: Choose cpufreq_conservative as scaling driver and execute
"echo disk > /sys/power/state".
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-06-25 11:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 11:57 bugme-daemon [this message]
2007-06-25 13:34 ` [Bug 8671] CPU frequency always on highest frequency after wakeup from suspend to disk bugme-daemon
[not found] ` <1182780094.22063.30.camel@queen.suse.de>
2007-06-25 14:11 ` Mattia Dongili
[not found] ` <1182784351.4249.3.camel@queen.suse.de>
[not found] ` <20070625153452.GC13308@inferi.kami.home>
[not found] ` <1182798023.4249.18.camel@queen.suse.de>
2007-06-26 6:22 ` [PATCH 2.6.22-rc6?] keep policy->user_policy in sync and use CPU0 policy as a template for other CPUs Mattia Dongili
2007-06-26 10:37 ` Thomas Renninger
2007-06-26 12:09 ` Mattia Dongili
2007-06-25 14:33 ` [Bug 8671] CPU frequency always on highest frequency after wakeup from suspend to disk bugme-daemon
2007-06-25 15:12 ` bugme-daemon
2007-06-25 16:18 ` bugme-daemon
2007-06-25 16:48 ` bugme-daemon
2007-06-25 16:55 ` bugme-daemon
2007-06-26 6:24 ` bugme-daemon
2007-06-26 6:24 ` bugme-daemon
2007-06-26 11:35 ` bugme-daemon
2007-06-26 12:58 ` bugme-daemon
2007-06-26 13:33 ` bugme-daemon
2007-06-26 13:57 ` Thomas Renninger
2007-06-26 20:31 ` Dave Jones
2007-06-27 9:28 ` Thomas Renninger
2007-06-28 4:16 ` Mattia Dongili
2007-06-26 14:12 ` bugme-daemon
2007-06-30 23:53 ` bugme-daemon
2007-07-01 0:00 ` bugme-daemon
2007-07-01 0:00 ` bugme-daemon
2007-08-08 16:57 ` bugme-daemon
2007-08-09 4:35 ` bugme-daemon
2007-08-09 14:07 ` bugme-daemon
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=bug-8671-3570@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.