From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65301] New: Cores stuck at max frequency after resume from suspend (Haswell)
Date: Thu, 21 Nov 2013 09:34:03 +0000 [thread overview]
Message-ID: <bug-65301-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=65301
Bug ID: 65301
Summary: Cores stuck at max frequency after resume from suspend
(Haswell)
Product: Power Management
Version: 2.5
Kernel Version: v3.12
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: zoku88@gmail.com
Regression: No
Created attachment 115381
--> https://bugzilla.kernel.org/attachment.cgi?id=115381&action=edit
ver_linux, cpuinfo and lspci outputs
The problem is that even though CPU usage is at ~0%, the cores are always stuck
at their max frequency after resume.
I thought this was related to https://bugzilla.kernel.org/show_bug.cgi?id=58971
However, I cloned the kernel git repo and checked out the commit that fixed
that bug (7dcd2677ea912573d9ed4bcd629b0023b2d11505), and the fix had no effect
(maybe SNB only?). So, this seems like it might have a different cause.
I have attached my system information.
As I've only had this laptop since around the time linux 3.11 came out, I'm not
really sure when the last time this didn't happen, though that commit seems to
have been made on top of one of the linux 3.10 rc's.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-11-21 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 9:34 bugzilla-daemon [this message]
2013-11-24 7:16 ` [Bug 65301] Cores stuck at max frequency after resume from suspend (Haswell) 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
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@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).