cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 42671] cpufreq userspace governor doesn't work on Intel Core 2 Gen 2 CPUs
Date: Tue, 31 Jan 2012 02:58:30 GMT	[thread overview]
Message-ID: <201201310258.q0V2wUuj022892@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42671-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42671


Len Brown <lenb@kernel.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |lenb@kernel.org




--- Comment #1 from Len Brown <lenb@kernel.org>  2012-01-31 02:58:30 ---
are you sure that you are using the userspace governor?
few people do, as it is generally obsolted by ondemand.

When ondemand is running, scaling_setspeed does nothing,
and you can "manually" control what ondemand does by
setting its maximum and minimum frequencies.

Please show the output from
grep .  /sys/devices/system/cpu/cpu0/cpufreq/*

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  reply	other threads:[~2012-01-31  2:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 19:43 [Bug 42671] New: cpufreq userspace governor doesn't work on Intel Core 2 Gen 2 CPUs bugzilla-daemon
2012-01-31  2:58 ` bugzilla-daemon [this message]
2012-01-31  6:57 ` [Bug 42671] " 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=201201310258.q0V2wUuj022892@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).