From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 42671] New: cpufreq userspace governor doesn't work on Intel Core 2 Gen 2 CPUs
Date: Fri, 27 Jan 2012 19:43:50 GMT [thread overview]
Message-ID: <bug-42671-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42671
Summary: cpufreq userspace governor doesn't work on Intel Core
2 Gen 2 CPUs
Product: Power Management
Version: 2.5
Kernel Version: All known
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: t.artem@mailcity.com
Regression: No
On my Intel Core i5 2500 CPU with acpi-cpufreq module loaded I do this
# echo 2000000 | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_setspeed
then
# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
2000000
2000000
2000000
2000000
so theoretically it should work.
However i7z (http://code.google.com/p/i7z/) shows that CPU frequency is freely
floating and turbo boost gets enabled as soon as I have any discernible load,
in other words userspace CPU frequency driver doesn't work at all and it
doesn't really enforce the specified CPU frequency.
--
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:[~2012-01-27 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 19:43 bugzilla-daemon [this message]
2012-01-31 2:58 ` [Bug 42671] cpufreq userspace governor doesn't work on Intel Core 2 Gen 2 CPUs bugzilla-daemon
2012-01-31 6:57 ` bugzilla-daemon
2012-02-05 22:04 ` bugzilla-daemon
2012-02-07 9:14 ` bugzilla-daemon
2012-05-13 14:28 ` 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-42671-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.