From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 57871] New: Cpu frequency scaling not working after waking up from suspend.
Date: Thu, 9 May 2013 14:08:29 +0000 (UTC) [thread overview]
Message-ID: <bug-57871-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=57871
Summary: Cpu frequency scaling not working after waking up from
suspend.
Product: Power Management
Version: 2.5
Kernel Version: 3.9
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: xdever@gmail.com
Regression: Yes
Created an attachment (id=101031)
--> (https://bugzilla.kernel.org/attachment.cgi?id=101031)
Dmesg, cpuinfo and kernel config
Environment: Thinkpad X220, Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, Gentoo
Description. I use 3.9 mainline kernel, with intel_pstate disabled (with intel
pstate it uses ~0.2W more power when reading pdf document than without it).
Since kernel 3.9, when my machine wakes up from suspend, in about 1 cases out
of 3 the CPU scaling won't work and the CPU-s are stucked at 2.7GHz maximal
speed. The machine becomes hot. Top shows nothing using the cpu. When I notice
that the machine is hot, I put it back to suspend, and when I wake it up again
it works as it should.
Attachements: I attached dmesg, cpuinfo and my kernel configuration. The dmesg
is long since the machine is running more than 1 days, but in the resume before
the last it was overheating and in the last one it is not overheating.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-05-09 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 14:08 bugzilla-daemon [this message]
2013-05-13 2:00 ` [Bug 57871] Cpu frequency scaling not working after waking up from suspend 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-57871-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 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.