From: "Doug Smythies" <dsmythies@telus.net>
To: 'Arto Jantunen' <viiru@iki.fi>
Cc: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
'Viresh Kumar' <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
'Srinivas Pandruvada' <srinivas.pandruvada@linux.intel.com>
Subject: RE: PROBLEM: Cpufreq constantly keeps frequency at maximum on 4.5-rc4
Date: Sat, 20 Feb 2016 08:31:18 -0800 [thread overview]
Message-ID: <000401d16bfc$21338450$639a8cf0$@net> (raw)
In-Reply-To: <87egc7ahqn.fsf@iki.fi>
On 2106.02.20 00:50 Arto Jantunen wrote:
> When using kernel 4.5-rc4 my Skylake machine runs very warm since all
> cpu cores are always kept at 3.10Ghz (with maximum without turboboost
> being 2.6Ghz), completely regardless of load. Swapping between the
> governors (performance and powersave) doesn't change the result in any
> way, frequency remains at a constant 3.10Ghz.
>
> The machine is using the intel_pstate driver, I don't know if it's
> possible to choose to use the acpi driver instead (without recompiling
> the kernel so that intel_pstate is not supported).
If you use grub then you can disable the intel_pstate driver by modifying
the grub command line. Here is an example, where I have left other stuff
that I use:
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 intel_pstate=disable net.ifnames=1 biosdevname=0"
Here is an example, with the intel_pstate directive by itself:
GRUB_CMDLINE_LINUX_DEFAULT="intel_pstate=disable"
If the intel_pstate driver is disabled, then the acpi-cpufreq CPU
frequency scaling driver will be used.
Remember to update grub after the above edit.
If you do not use grub, then I don't know.
Please, and as a test, also try this and report back:
GRUB_CMDLINE_LINUX_DEFAULT="intel_pstate=no_hwp"
> I can force the frequency down manually with cpufreq-set, so the problem
> doesn't seem to be with the actual frequency changing.
> Cpuinfo (taken from 4.4 which doesn't have the problem):
Is kernel 4.5-rc4 the first one you have tried in the 4.5 series?
What I am asking is if you know if the issue was introduced between
kernels 4.4 and 4.5-rc1 (most likely) or between 4.5-rc3 and 4.5-rc4 or?
What distribution, if any, of Linux do you use?
It might make sense to take this off-list and into a bugzilla bug report.
... Doug
next prev parent reply other threads:[~2016-02-20 16:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 8:49 PROBLEM: Cpufreq constantly keeps frequency at maximum on 4.5-rc4 Arto Jantunen
2016-02-20 16:31 ` Doug Smythies [this message]
2016-02-20 17:10 ` Arto Jantunen
2016-02-20 18:03 ` Chen, Yu C
2016-02-21 8:45 ` Arto Jantunen
2016-02-21 8:52 ` Chen, Yu C
2016-02-21 20:02 ` Srinivas Pandruvada
2016-02-21 20:33 ` Arto Jantunen
2016-02-22 6:16 ` Viresh Kumar
2016-02-22 16:39 ` Arto Jantunen
2016-02-22 16:41 ` Viresh Kumar
2016-02-22 16:48 ` Viresh Kumar
2016-02-22 19:25 ` Srinivas Pandruvada
2016-02-28 15:43 ` Arto Jantunen
2016-02-29 6:22 ` Doug Smythies
2016-03-01 19:28 ` Doug Smythies
2016-02-29 16:49 ` Srinivas Pandruvada
2016-03-01 0:37 ` Rafael J. Wysocki
[not found] ` <20160229201946.0bdcc48e@annuminas.surriel.com>
2016-03-01 7:06 ` Arto Jantunen
2016-03-01 16:59 ` Arto Jantunen
2016-03-01 19:22 ` Rik van Riel
2016-03-01 19:47 ` Arto Jantunen
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='000401d16bfc$21338450$639a8cf0$@net' \
--to=dsmythies@telus.net \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viiru@iki.fi \
--cc=viresh.kumar@linaro.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).