From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 86461] New: intel_pstate does not obey min/max frequencies set by user
Date: Fri, 17 Oct 2014 09:21:52 +0000 [thread overview]
Message-ID: <bug-86461-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=86461
Bug ID: 86461
Summary: intel_pstate does not obey min/max frequencies set by
user
Product: Power Management
Version: 2.5
Kernel Version: 3.17-rc5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: patrakov@gmail.com
Regression: No
# uname -a
Linux aep-vaio 3.17.0-rc5 #1 SMP PREEMPT Thu Sep 18 23:13:08 YEKT 2014 x86_64
Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz GenuineIntel GNU/Linu
# echo 2400000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 0.97 ms.
hardware limits: 800 MHz - 3.50 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 2.40 GHz and 3.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 804 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: intel_pstate
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 0.97 ms.
hardware limits: 800 MHz - 3.50 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 2.40 GHz and 3.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 885 MHz (asserted by call to hardware).
analyzing CPU 2:
driver: intel_pstate
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 0.97 ms.
hardware limits: 800 MHz - 3.50 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 2.40 GHz and 3.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 3:
driver: intel_pstate
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 0.97 ms.
hardware limits: 800 MHz - 3.50 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 2.40 GHz and 3.50 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 822 MHz (asserted by call to hardware).
As you see, my attempt to force the minimum frequency to 2.4 GHz has been
ignored.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-10-17 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 9:21 bugzilla-daemon [this message]
2014-10-17 15:17 ` [Bug 86461] intel_pstate does not obey min/max frequencies set by user bugzilla-daemon
2014-10-17 16:43 ` bugzilla-daemon
2014-10-17 16:51 ` bugzilla-daemon
2014-10-17 17:02 ` bugzilla-daemon
2014-10-17 17:28 ` bugzilla-daemon
2014-10-23 13:57 ` bugzilla-daemon
2014-10-28 5:17 ` bugzilla-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-86461-12968@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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).