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: Tue, 26 Nov 2013 01:20:00 +0000 [thread overview]
Message-ID: <bug-65301-12968-m9cyL6xZXH@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 #8 from Mykal Valentine <zoku88@gmail.com> ---
Marcin: I'm not sure if that's the exact same problem, given that resuming from
suspend to RAM was what I was filing the bug on, which seems to function as a
workaround for another issue that you're seeing.
Unfortunately, I wasn't very clear with the original bug report to state that.
Incidentally, I haven't tested resume from hibernate.
Also, since there was a bug in i915 for SNB, you should make sure that you're
not hitting that bug. I wasn't sure what version that bug fix got in (either
3.11 or 3.12), but I would recommend trying 3.12 on your system to see if the
problem persists, just in case 3.11 didn't have the fix. Or checking
out/compiling commit 7dcd2677ea912573d9ed4bcd629b0023b2d11505 to see if that
fixes your problem.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-11-26 1:20 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
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 [this message]
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-m9cyL6xZXH@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).