From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low
Date: Mon, 05 May 2014 18:05:11 +0000 [thread overview]
Message-ID: <bug-75121-12968-ptcCEdLGWv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75121-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75121
--- Comment #16 from Dirk Brandewie <dirk.brandewie@gmail.com> ---
(In reply to Doug Smythies from comment #15)
> Created attachment 135151 [details]
> Just another method I tried. Phoronix ffmpeg test is as fast as performance
> mode with this method.
>
> Hi Dirk: Did you ever figure out for certain why some had the CPU freq
> remains high after suspend issue? It remains unclear to me, and I do not
> know how to even try to re-create here on my test computer.
>
I could make it happen occasionally on my ivy bridge laptop test system.
I think it have to the hardware coordination on the chip but I haven't
proven that.
> References (some but not all):
> https://bugzilla.kernel.org/show_bug.cgi?id=66581#c21
> https://bugzilla.kernel.org/show_bug.cgi?id=66581#c26
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-05-05 18:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 23:47 [Bug 75121] New: Intel Pstate driver - powersave mode - CPU frequency too low bugzilla-daemon
2014-04-29 23:54 ` [Bug 75121] " bugzilla-daemon
2014-04-29 23:56 ` bugzilla-daemon
2014-04-29 23:59 ` bugzilla-daemon
2014-04-30 0:08 ` bugzilla-daemon
2014-05-02 14:25 ` bugzilla-daemon
2014-05-02 23:42 ` bugzilla-daemon
2014-05-02 23:58 ` bugzilla-daemon
2014-05-03 0:03 ` bugzilla-daemon
2014-05-03 0:05 ` bugzilla-daemon
2014-05-03 0:11 ` bugzilla-daemon
2014-05-03 0:19 ` bugzilla-daemon
2014-05-03 0:47 ` bugzilla-daemon
2014-05-03 0:47 ` bugzilla-daemon
2014-05-03 3:49 ` bugzilla-daemon
2014-05-03 3:58 ` bugzilla-daemon
2014-05-03 4:59 ` bugzilla-daemon
2014-05-03 5:00 ` bugzilla-daemon
2014-05-04 19:18 ` bugzilla-daemon
2014-05-05 18:05 ` bugzilla-daemon [this message]
2014-05-05 18:52 ` bugzilla-daemon
2014-05-08 22:19 ` bugzilla-daemon
2014-05-08 22:21 ` bugzilla-daemon
2014-05-08 22:26 ` bugzilla-daemon
2014-05-28 21:22 ` bugzilla-daemon
2014-06-03 20:45 ` bugzilla-daemon
2015-07-21 19:28 ` 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-75121-12968-ptcCEdLGWv@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;
as well as URLs for NNTP newsgroup(s).