Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #167131 > unrolled thread

Who's playing with scaling_max_freq?

Started byStefan Monnier <monnier@iro.umontreal.ca>
First post2016-04-27 03:00 +0200
Last post2016-04-28 19:40 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.user


Contents

  Who's playing with scaling_max_freq? Stefan Monnier <monnier@iro.umontreal.ca> - 2016-04-27 03:00 +0200
    Re: Who's playing with scaling_max_freq? humbert.olivier.1@free.fr - 2016-04-28 02:50 +0200
      Re: Who's playing with scaling_max_freq? Stefan Monnier <monnier@iro.umontreal.ca> - 2016-04-28 05:30 +0200
        Re: Who's playing with scaling_max_freq? deloptes <deloptes@gmail.com> - 2016-04-28 22:10 +0200
    Re: joe____Get_a_Samsung_Galaxy-S7 Joe Thompson <mydodge413@gmail.com> - 2016-04-28 19:40 +0200

#167131 — Who's playing with scaling_max_freq?

FromStefan Monnier <monnier@iro.umontreal.ca>
Date2016-04-27 03:00 +0200
SubjectWho's playing with scaling_max_freq?
Message-ID<rslZD-sA-3@gated-at.bofh.it>
Max scaling_max_freq seems stuck at 1GHz even though it should be able
to go up to 1.83GHz.

    # echo 1833000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
    1000000
    # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 
    1833000 1333000 1000000 
    #

This is on a Thinkpad T60 running Debian stable.  Any idea what might be
causing this?  Or at least, which part of the system might cause
scaling_max_freq to be (re)set to 1GHz right after I force-set it to 1.83GHz?
Would it be some daemon like systemd or rather than kernel?

This Thinkpad T60 is actually used as a desktop: it's parked in a dock
(with the lid is closed) where I have it connected to a keyboard and monitor.


        Stefan

[toc] | [next] | [standalone]


#167166

Fromhumbert.olivier.1@free.fr
Date2016-04-28 02:50 +0200
Message-ID<rsIjw-2g8-7@gated-at.bofh.it>
In reply to#167131
You might need to relaunch :
invoke-rc.d cpufrequtils restart
or maybe :
/etc/init.d/cpufrequtils restart

or something around this (at the top of my head).
Hope that helps.
Olivier

----- Mail original -----
De: "Stefan Monnier" <monnier@iro.umontreal.ca>
À: debian-user@lists.debian.org
Envoyé: Mercredi 27 Avril 2016 02:50:13
Objet: Who's playing with scaling_max_freq?

Max scaling_max_freq seems stuck at 1GHz even though it should be able
to go up to 1.83GHz.

    # echo 1833000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq; cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
    1000000
    # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 
    1833000 1333000 1000000 
    #

This is on a Thinkpad T60 running Debian stable.  Any idea what might be
causing this?  Or at least, which part of the system might cause
scaling_max_freq to be (re)set to 1GHz right after I force-set it to 1.83GHz?
Would it be some daemon like systemd or rather than kernel?

This Thinkpad T60 is actually used as a desktop: it's parked in a dock
(with the lid is closed) where I have it connected to a keyboard and monitor.


        Stefan

[toc] | [prev] | [next] | [standalone]


#167169

FromStefan Monnier <monnier@iro.umontreal.ca>
Date2016-04-28 05:30 +0200
Message-ID<rsKOl-4pk-5@gated-at.bofh.it>
In reply to#167166
> You might need to relaunch :
> invoke-rc.d cpufrequtils restart
> or maybe :
> /etc/init.d/cpufrequtils restart

Thanks, but I don't have cpufrequtils installed.  Also, AFAIK
cpufrequtils works by fiddling with those /sys nodes just like I do
(once and for all), so it wouldn't cause such on-the-fly-resetting of
scaling_max_freq.


        Stefan

[toc] | [prev] | [next] | [standalone]


#167183

Fromdeloptes <deloptes@gmail.com>
Date2016-04-28 22:10 +0200
Message-ID<rt0q5-1AY-1@gated-at.bofh.it>
In reply to#167169
Stefan Monnier wrote:

>> You might need to relaunch :
>> invoke-rc.d cpufrequtils restart
>> or maybe :
>> /etc/init.d/cpufrequtils restart
> 
> Thanks, but I don't have cpufrequtils installed.  Also, AFAIK
> cpufrequtils works by fiddling with those /sys nodes just like I do
> (once and for all), so it wouldn't cause such on-the-fly-resetting of
> scaling_max_freq.
> 
> 
>         Stefan

check for the right governor (ondemand) you shouldn't care. in some cases
though you must set yourself. this could be kernel or systemd related -
this changed recently to newer version together with udev.
I had a case that cpu was always at max freq - I had to edit the cpufreq in 
cat /etc/default/cpufrequtils
GOVERNOR="ondemand"
MAX_SPEED="3.6GHz"
MIN_SPEED="1.4GHz"

hope it helps

[toc] | [prev] | [next] | [standalone]


#167178 — Re: joe____Get_a_Samsung_Galaxy-S7

FromJoe Thompson <mydodge413@gmail.com>
Date2016-04-28 19:40 +0200
SubjectRe: joe____Get_a_Samsung_Galaxy-S7
Message-ID<rsY4V-7Js-3@gated-at.bofh.it>
In reply to#167131

[Multipart message — attachments visible in raw view] — view raw

Ok

On Thursday, April 28, 2016, <mydodge413@gmail.com> wrote:

> hi _Get_a_Samsung_Galaxy-S7 www.%%%%.yours7.ml



-- 
Sent from Gmail Mobile

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web