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 20:22:19 +0000 [thread overview]
Message-ID: <bug-65301-12968-2RZ3XCQmib@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 #6 from tomasi <tomas.ivanek@gmail.com> ---
Hi,
Whole CPU frequency managment is broken somehow.
i5-4200U CPU @ 1.60GHz CPU should support 800 Mhz, But i see it's running at
least on 1.6 Ghz. (After suspend/resume It's running in Turbo mode)
bio@dell-xps:/sys/devices/system/cpu/intel_pstate$ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 0.97 ms.
hardware limits: 800 MHz - 2.60 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 800 MHz and 2.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-11-25 20:22 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 [this message]
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-2RZ3XCQmib@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).