linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: lists@ssl-mail.com
Cc: linux-pm@vger.kernel.org
Subject: RE: Can't enable/switch to 'schedutil' governor with kernel 4.7.2 ?
Date: Wed, 24 Aug 2016 16:51:26 -0700	[thread overview]
Message-ID: <002401d1fe62$6ea9d8d0$4bfd8a70$@net> (raw)
In-Reply-To: <1472068841.1982612.705147345.1DDE879C@webmail.messagingengine.com>

On 2016.08.24  13:01 lists@ssl-mail.com wrote:
> On Tue, Aug 23, 2016, at 02:23 PM, Doug Smythies wrote:
>> On 2016.08.23 09:25 lists@ssl-mail.com wrote:
>> 
>>> Can't enable/switch to 'schedutil' governor
>>> I'm running 
>>>	uname -rm
>>>		4.7.2-1.g34ba8d6-default x86_64
>>>
>>> I'm trying to set/use the 'schedutil' governor.
>>
>> ...[cut]...
>> 
>> Please try not using cpupower or any other utility.
>> Please try using the primitive commands directly.

> as a general rule?

That is up to you. Myself, I never use other utilities
or tools if I can avoid it (and this issue is a good
example as to why).

> or in this case?

Yes, in this case as a way to separate the variables.
If you use a separate tool then you don't know if the
problem is in the tool or the kernel.

> IT appears the problem's actually a kernel bug:
>
> Bug 135391 - cpupower does not change the governor anymore 
> https://bugzilla.kernel.org/show_bug.cgi?id=135391

No, that looks to me like a bug in the tool/utility and not
the kernel itself.

> AFAICT the fix isn't in the 4.7.X tree, just in the 4.8.X one.



      reply	other threads:[~2016-08-25  4:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 16:25 Can't enable/switch to 'schedutil' governor with kernel 4.7.2 ? lists
2016-08-23 21:23 ` Doug Smythies
2016-08-24 20:00   ` lists
2016-08-24 23:51     ` Doug Smythies [this message]

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='002401d1fe62$6ea9d8d0$4bfd8a70$@net' \
    --to=dsmythies@telus.net \
    --cc=linux-pm@vger.kernel.org \
    --cc=lists@ssl-mail.com \
    /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).