From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 66581] New: intel_pstate/powersave - cpu frequency remains at high level (Turbo) after suspend/resume
Date: Thu, 05 Dec 2013 09:36:53 +0000 [thread overview]
Message-ID: <bug-66581-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=66581
Bug ID: 66581
Summary: intel_pstate/powersave - cpu frequency remains at high
level (Turbo) after suspend/resume
Product: Power Management
Version: 2.5
Kernel Version: Linux genlap 3.12.2-gentoo #3 SMP Wed Dec 4 19:19:01
CET 2013 x86_64 Intel(R) Core(TM) i7-4900MQ CPU @
2.80GHz GenuineIntel GNU/Linux
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: herrlado@gmail.com
Regression: No
Created attachment 117541
--> https://bugzilla.kernel.org/attachment.cgi?id=117541&action=edit
outpot of cpupower
After resume all the cores are showing the max turbo frequences for my cpu.
This is unrealisitc as the max frequence is 2.80 and all the cores can not run
at the max turbo frequence.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-12-05 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 9:36 bugzilla-daemon [this message]
2013-12-05 9:37 ` [Bug 66581] intel_pstate/powersave - cpu frequency remains at high level (Turbo) after suspend/resume bugzilla-daemon
2013-12-05 9:37 ` bugzilla-daemon
2013-12-05 9:38 ` bugzilla-daemon
2013-12-05 14:42 ` bugzilla-daemon
2013-12-05 19:35 ` bugzilla-daemon
2013-12-05 19:35 ` bugzilla-daemon
2013-12-05 19:45 ` bugzilla-daemon
2013-12-06 21:02 ` bugzilla-daemon
2013-12-09 5:52 ` bugzilla-daemon
2013-12-09 13:31 ` bugzilla-daemon
2013-12-10 9:10 ` 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-66581-12968@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