From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10982] New: scaling_max_freq locked
Date: Wed, 25 Jun 2008 14:22:52 -0700 (PDT) [thread overview]
Message-ID: <bug-10982-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=10982
Summary: scaling_max_freq locked
Product: Power Management
Version: 2.5
KernelVersion: 2.6.25
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: nicolas.vinot@gmail.com
Distribution: Debian testing
Hardware Environment: IBM Thinkpad T42
Software Environment: 2.6.25 kernel
Problem Description:
Few minutes after boot, scaling_max_freq is locked to the lowest cpu speed.
Impossible to change it, even by hand or cpufreq-set.
root:cpufreq# pwd
/sys/devices/system/cpu/cpu0/cpufreq
root:cpufreq# cat scaling_driver
acpi-cpufreq
root:cpufreq# cat scaling_available_frequencies
1800000 1600000 1400000 1200000 1000000 800000 600000
root:cpufreq# cat scaling_available_governors
powersave userspace ondemand conservative performance
root:cpufreq# cat scaling_governor
ondemand
root:cpufreq# cat scaling_max_freq
600000
root:cpufreq# echo 1800000 > scaling_max_freq
root:cpufreq# cat scaling_max_freq
600000
root:cpufreq# cat cpuinfo_max_freq
1800000
root:cpufreq# cat cpuinfo_max_freq > scaling_max_freq
root:cpufreq# cat scaling_max_freq
600000
root:cpufreq# cpufreq-set -u 1800000
root:cpufreq# cat scaling_max_freq
600000
Before value locking, cpufreq works perfectly as it should.
This problem often occurs when the processor heats (high load, compilation...)
but randomly too (few minutes after boot, even if it does nothing).
Sometimes, after cpu cooling or cpufreqd reboot, I can manage again the speed
by hand.
My old kernel version (2.6.18 with speedstep-centrino driver) hasn't this
problem and cpufreqd works perfectly on it.
--
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:[~2008-06-25 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 21:22 bugme-daemon [this message]
2008-06-25 22:25 ` [Bug 10982] scaling_max_freq locked - Thinkpad T42 bugme-daemon
2008-06-25 22:32 ` bugme-daemon
2008-06-26 11:37 ` bugme-daemon
2008-06-26 12:30 ` bugme-daemon
2008-06-27 18:43 ` 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-10982-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 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).