FS#35588 - [cpupower] Tuning governors does not work as described

Attached to Project: Community Packages
Opened by Florian Scandella (fscan) - Saturday, 01 June 2013, 16:15 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 02 July 2013, 18:30 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Tuning cpufreq governors does not work like described in https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling#Tuning_governors_.28with_cpupower.29 if the governor is not ondemand (default).

Because the governor is set after the commands in /etc/defaults/cpupower are executed the sysfs files do not exist at this point.

# systemctl status cpupower
cpupower.service - Apply cpupower configuration
Loaded: loaded (/usr/lib/systemd/system/cpupower.service; enabled)
Active: active (exited) since Sat 2013-06-01 17:36:35 CEST; 2min 5s ago
Process: 275 ExecStart=/usr/lib/systemd/scripts/cpupower (code=exited, status=0/SUCCESS)

Jun 01 17:36:35 spellcaster cpupower[275]: /etc/default/cpupower: line 34: /sys/devices/system/cpu/cpufreq/conservative/up_threshold: No such file or directory
Jun 01 17:36:35 spellcaster cpupower[275]: /etc/default/cpupower: line 35: /sys/devices/system/cpu/cpufreq/conservative/down_threshold: No such file or directory
Jun 01 17:36:35 spellcaster cpupower[275]: /etc/default/cpupower: line 36: /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor: No such file or directory
Jun 01 17:36:35 spellcaster cpupower[275]: /etc/default/cpupower: line 37: /sys/devices/system/cpu/cpufreq/conservative/freq_step: No such file or directory
Jun 01 17:36:35 spellcaster systemd[1]: Started Apply cpupower configuration.
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 02 July 2013, 18:30 GMT
Reason for closing:  Fixed
Comment by Sébastien Luttringer (seblu) - Tuesday, 02 July 2013, 18:29 GMT
Your analyse is right. the tip provided is useless and executing commands in a config file is a dirty hack.
I deleted it. Next time, you could fix the wiki by yourself, no need to open a bug report.

Loading...