From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65301] Cores stuck at max frequency after resume from suspend (Haswell)
Date: Mon, 25 Nov 2013 03:09:26 +0000 [thread overview]
Message-ID: <bug-65301-12968-Mpl83WYEgx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65301-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65301
--- Comment #3 from Mykal Valentine <zoku88@gmail.com> ---
I'm not really sure. I know it definitely didn't work normally in 3.11 or that
version of 3.10rc that I pulled that had the i915 bug fix either.
I think versions before that commit would run into the i915 bug, though. which
I think also causes the frequency for the cores to stay high after resume.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-11-25 3:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 9:34 [Bug 65301] New: Cores stuck at max frequency after resume from suspend (Haswell) bugzilla-daemon
2013-11-24 7:16 ` [Bug 65301] " bugzilla-daemon
2013-11-25 2:08 ` bugzilla-daemon
2013-11-25 3:09 ` bugzilla-daemon [this message]
2013-11-25 3:28 ` bugzilla-daemon
2013-11-25 9:08 ` bugzilla-daemon
2013-11-25 20:22 ` bugzilla-daemon
2013-11-25 22:15 ` bugzilla-daemon
2013-11-26 1:20 ` bugzilla-daemon
2013-11-28 8:15 ` bugzilla-daemon
2013-12-09 3:26 ` bugzilla-daemon
2013-12-09 5:49 ` bugzilla-daemon
2013-12-09 5:52 ` 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-65301-12968-Mpl83WYEgx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.