From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 58801] intel_pstate/powersave - cpu frequency remains at high level if if system is idle
Date: Sat, 25 May 2013 09:39:03 +0000 (UTC) [thread overview]
Message-ID: <20130525093903.3768711F965@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-58801-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=58801
--- Comment #2 from Christoph Loehr <c.h.l@web.de> 2013-05-25 09:39:02 ---
At first I have to add that also kernel 3.9.2 worked. According to the
changelog of kernel 3.9.3 between 3.9.2 and 3.9.3 three commitments concerning
intel_pstate (b540137a810d0267051c538e68d4348e43a1edf3,
2aa491f8bdcac932006548b1a2b655b29c942e08 and
1abc4b20b85b42e8573957e54b193385cf48b0d6) have been added to the kernel. I
guess that one of them might be the culprit.
As I am rather a user it's only possible for me to describe the symptoms.
With kernel 3.9.2, when the system is idle according to cpufreg-info the
frequency of all cpu's is between 775 and 800 MHz, which is the minimum. With
kernel 3.9.3 and 3.9.4 it never goes below 2.85 GHz. In both cases intel_pstate
is the driver and powersave the governor.
Christoph
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-25 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 7:24 [Bug 58801] New: intel_pstate/powersave - cpu frequency remains at high level if if system is idle bugzilla-daemon
2013-05-25 9:07 ` [Bug 58801] " bugzilla-daemon
2013-05-25 9:16 ` [Bug 58801] New: " Rafael J. Wysocki
2013-05-25 9:39 ` bugzilla-daemon [this message]
2013-05-25 14:57 ` [Bug 58801] " bugzilla-daemon
2013-05-25 16:30 ` bugzilla-daemon
2013-05-25 17:34 ` bugzilla-daemon
2013-05-27 4:05 ` 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=20130525093903.3768711F965@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