From: "Doug Smythies" <dsmythies@telus.net>
To: 'Martin Steigerwald' <martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
'Kristen Carlson Accardi' <kristen@linux.intel.com>
Subject: RE: [BUG] ThinkPad T520 overheating with P-State driver
Date: Wed, 6 May 2015 19:51:19 -0700 [thread overview]
Message-ID: <000601d08870$b2979e60$17c6db20$@net> (raw)
In-Reply-To: <2208008.uDRZL3Gdb7@merkaba>
On 2015.05.06 13:37 Martin Steigerwald wrote:
> I get frequencies like:
>
> 3080566
> 3068945
> 3009082
> 2999902
Please know that the intel_pstate driver reports actual CPU frequencies
over the last sample interval. In terms of heat, they don't mean anything,
you would have to look at how much time the CPU spent in the C0 and other states.
> Yet with acpi-cpufreq without limiting maximum performance at all, I get the
> following with the *same* workload:
> 2501000
> 2501000
> 1000000
> 1000000
Please know that the acpi-cpufreq driver reports what frequency (pstate)
It is asking for, not what might actually be happening.
If your CPU 2 and 3 were ever active during that sample time
They would be at the same frequency as your turbostate CPU 0 or 1,
which ever is higher.
> There is also some other bug report about this:
> Please change intel_pstate default to disable
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647
> appears to be quite old, but still seems unresolved.
That bug report is very old, and is closed.
I made a late entry on that bug report on 2014.06.08,
and have submitted a patch set to deal with, among other things,
the long duration issue.
next prev parent reply other threads:[~2015-05-07 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 20:36 [BUG] ThinkPad T520 overheating with P-State driver Martin Steigerwald
2015-05-07 2:51 ` Doug Smythies [this message]
2015-05-07 8:20 ` Martin Steigerwald
2015-05-07 14:47 ` Doug Smythies
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='000601d08870$b2979e60$17c6db20$@net' \
--to=dsmythies@telus.net \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin@lichtvoll.de \
/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).