From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 66581] intel_pstate/powersave - cpu frequency remains at high level (Turbo) after suspend/resume
Date: Thu, 05 Dec 2013 19:45:20 +0000 [thread overview]
Message-ID: <bug-66581-12968-aDFXNiQNNl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-66581-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=66581
--- Comment #7 from Lado Kumsiashvili <herrlado@gmail.com> ---
OK, attached. Another strange thing. I think I have never noticed before,
because I have this laptop since a couple of days. After I have booted cpufreq
showed 2.80ghz at all cores without any last. THen I have executed
max_perf_pct showed 100
and min_perf_pct showed 21
I has never gone below 2.80Ghz
After I have executed
echo 21 > /sys/devices/system/cpu/intel_pstate/max_perf_pct
it went down to 800Mhz as expected in cpupower tool view
genlap ~ # cpupower -c 0-4 frequency-info | grep current
current policy: frequency should be within 800 MHz and 3.80 GHz.
current CPU frequency is 800 MHz (asserted by call to hardware).
current policy: frequency should be within 800 MHz and 3.80 GHz.
current CPU frequency is 800 MHz (asserted by call to hardware).
current policy: frequency should be within 800 MHz and 3.80 GHz.
current CPU frequency is 800 MHz (asserted by call to hardware).
current policy: frequency should be within 800 MHz and 3.80 GHz.
current CPU frequency is 800 MHz (asserted by call to hardware).
current policy: frequency should be within 800 MHz and 3.80 GHz.
current CPU frequency is 800 MHz (asserted by call to hardware).
current CPU frequency is 800 MHz (asserted by call to hardware).
When I put the value 100 in the max_perf_pct it goes now between 2.80 and
somewhere 3.30Ghz and changes all the time as I execute cpupower.
But, before I have touched this max_perf_pct after the boot it was constantly
on 2.80.
With regards,
Lado
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-12-05 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 9:36 [Bug 66581] New: intel_pstate/powersave - cpu frequency remains at high level (Turbo) after suspend/resume bugzilla-daemon
2013-12-05 9:37 ` [Bug 66581] " bugzilla-daemon
2013-12-05 9:37 ` bugzilla-daemon
2013-12-05 9:38 ` bugzilla-daemon
2013-12-05 14:42 ` bugzilla-daemon
2013-12-05 19:35 ` bugzilla-daemon
2013-12-05 19:35 ` bugzilla-daemon
2013-12-05 19:45 ` bugzilla-daemon [this message]
2013-12-06 21:02 ` bugzilla-daemon
2013-12-09 5:52 ` bugzilla-daemon
2013-12-09 13:31 ` bugzilla-daemon
2013-12-10 9:10 ` 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-66581-12968-aDFXNiQNNl@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