From: Andy Lutomirski <luto@amacapital.net>
To: Dieter Mummenschanz <dmummenschanz@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: intel_pstate: Haswell i7-4600M refuses to enter lower Package States
Date: Tue, 25 Feb 2014 18:48:58 -0800 [thread overview]
Message-ID: <530D561A.4030509@mit.edu> (raw)
In-Reply-To: <trinity-4cc330c5-5df6-41ca-99e3-ea6a43c4ed56-1392899382625@3capp-gmx-bs46>
On 02/20/2014 04:29 AM, Dieter Mummenschanz wrote:
> Hello,
>
> on my Lenovo T440p Laptop the Haswell i7-4600M CPU refuses to enter lower PC states resulting in 14-15 Watts continuous power drain even if the system is idle and every tunalbes in powertop 2.5 are enabled. The issue is reproducable with Kernel versions 3.13 up to 3.14-rc3.
>
> Did anyone else experience a similar issue?
Something's confused here. Do you mean P-states (i.e. performance
states or "frequency" settings) or PC-states (i.e. "package C-states")?
I suspect that you mean the latter, in which case intel_pstate has
nothing to do with the problem.
The relevant diagnostic is the output from turbostat.
--Andy
prev parent reply other threads:[~2014-02-26 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 12:29 intel_pstate: Haswell i7-4600M refuses to enter lower Package States Dieter Mummenschanz
2014-02-26 2:48 ` Andy Lutomirski [this message]
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=530D561A.4030509@mit.edu \
--to=luto@amacapital.net \
--cc=dmummenschanz@gmx.de \
--cc=linux-kernel@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