You are not logged in.
I have a laptop with processor Intel-M (M-5Y71) and I am used to run it always on the lowest frequency.
In order to archieve this behaviour I disable intel_pstate on kernel line and set frequency with cpupower.
So far, everything worked as intended unitl I upgraded cpupower to 4.7.1.
After the upgrade I still can set the frequency, but it no longer holds the frequency constant (and behaves as if with a intel_pstate driver on).
My question is. Is this a regression of cpupower? After downgrading to the previous version I have achieved the inteded behaviour.
If this is a bug, how should it be reported?
Last edited by e.sovetkin (2016-08-19 07:43:19)
Offline
I have a similar issue when changing governor policies:
sudo cpupower frequency-set -g performance
This no longer sets the the current governor policy for all CPU's and shows no output in the terminal. My laptop uses powersave by default and it remains the current policy.
Last edited by monotykamary (2016-07-31 02:46:36)
Offline
Same over here, downgraded cpupower (4.7-1 -> 4.6-4) to fix for now...
Offline
I noticed also that there no output is given with 4.7-1, normally cpupower notifies if it sets the frequency succefully.
I have submitted a bug report
https://bugs.archlinux.org/task/50209
so, those who have a problem are welcomed to add their details and vote.
Offline
Same here. Can't set governor, performance bias gets set normally.
Offline
Hi:
Try
root only
# echo "conservative" >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Change "conservative" by your favorite governor
Verify:
# cpupower frecquency-info
Try...try
La verdad está dormida en la mente de cada Hombre
Offline
Hi:
Try
root only
# echo "conservative" >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Change "conservative" by your favorite governor
Verify:
# cpupower frecquency-info
Try...try
Per the wiki, that works of course. But cpupower no longer does. It detects the governor correctly when it is changed that way, the problem is that it's not changing it.
Offline
This is definitely a regression that is not specific to one architecture. Hopefully the authors of cpupower can fix it.
Offline
Same here. Cpupower is unable to change anything (governor or frequency). Downgrading to version 4.6-4 fixes it for now.
EDIT
According to the upstream bug report there should be a fix in the upcoming version (4.8).
Last edited by koassim (2016-08-13 10:04:19)
Offline