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 14:57:22 +0000 (UTC) [thread overview]
Message-ID: <20130525145722.39D3E11F976@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-58801-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=58801
--- Comment #3 from Christoph Loehr <c.h.l@web.de> 2013-05-25 14:57:21 ---
In the meantime I have made a git bisect between kernel 3.9.2 and 3.9.3 with
the following result:
5aacc8bcf0b23e20cbb205ac6fdc3ce797e1cae2 is the first bad commit
commit 5aacc8bcf0b23e20cbb205ac6fdc3ce797e1cae2
Author: Dirk Brandewie <dirk.j.brandewie@intel.com>
Date: Tue May 7 08:20:25 2013 -0700
cpufreq / intel_pstate: remove idle time and duration from sample and
calculations
commit 1abc4b20b85b42e8573957e54b193385cf48b0d6 upstream.
In order to confirm this is the relevant commit I have compiled a 3.9.3 kernel
where I had reverted the changes provided by this commit. With this kernel
booted the frequency switching works again.
I hope that helps.
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 14:57 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 ` [Bug 58801] " bugzilla-daemon
2013-05-25 14:57 ` bugzilla-daemon [this message]
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=20130525145722.39D3E11F976@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