From: Rik van Riel <riel@redhat.com>
To: Arto Jantunen <viiru@iki.fi>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: PROBLEM: Cpufreq constantly keeps frequency at maximum on 4.5-rc4
Date: Tue, 01 Mar 2016 14:22:55 -0500 [thread overview]
Message-ID: <1456860175.25322.59.camel@redhat.com> (raw)
In-Reply-To: <87twkqllst.fsf@kirika.int.wmdata.fi>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Tue, 2016-03-01 at 09:06 +0200, Arto Jantunen wrote:
> Rik van Riel <riel@redhat.com> writes:
>
> > What exactly is the problem you are seeing, and on what CPUs?
>
> Quoting from the first mail in this thread:
>
> 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.
> > What does the cpufreq table for that CPU look like?
> >
> > Does HLT (or its equivalent) have a really, really high
> > exit or residency latency?
>
> I don't know the answer to either of these questions. How do I find
> out?
Could you run this?
#!/bin/sh
for i in `seq 0 10`; do
if [ -d /sys/devices/system/cpu/cpu0/cpuidle/state$i ]; then
echo -n "state $i latency: "
cat
/sys/devices/system/cpu/cpu0/cpuidle/state$i/latency
fi
done
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-01 19:22 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
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 [this message]
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=1456860175.25322.59.camel@redhat.com \
--to=riel@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=viiru@iki.fi \
/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).