From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 80651] New: [intel_pstate] pstate settings are lost during suspend/resume cycle
Date: Fri, 18 Jul 2014 22:37:22 +0000 [thread overview]
Message-ID: <bug-80651-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=80651
Bug ID: 80651
Summary: [intel_pstate] pstate settings are lost during
suspend/resume cycle
Product: Power Management
Version: 2.5
Kernel Version: 3.15.6
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: liquid.acid@gmx.net
Regression: No
Created attachment 143431
--> https://bugzilla.kernel.org/attachment.cgi?id=143431&action=edit
dmesg output
Hello,
the patches that went into 3.15.6 made the intel_pstate driver finally useable
for me. At least as long as I don't suspend/resume the system.
After resume the multiplicator is locked to the highest one. I have to change
min_perf_pct and max_perf_pct to some other values and then back to restore the
behaviour before the suspend.
CPU is a Haswell / i7-4700HQ.
With best wishes,
Tobias
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-07-18 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 22:37 bugzilla-daemon [this message]
2014-07-18 22:37 ` [Bug 80651] [intel_pstate] pstate settings are lost during suspend/resume cycle bugzilla-daemon
2014-07-18 22:38 ` bugzilla-daemon
2014-07-18 22:41 ` bugzilla-daemon
2014-07-20 10:43 ` bugzilla-daemon
2014-07-21 2:19 ` 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-80651-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).