You are not logged in.
Pages: 1
Out of the blue, I noticed that it looks like cpufrequtils isn't working correctly for me anymore (it did before).
Even when it is set to the powersave governor and very little is running, it always runs at the maximum CPU freq now.
$ uptime
17:41:30 up 14 min, 1 user, load average: 0.02, 0.08, 0.10
$ cpufreq-info -p
1600000 1862000 powersave
$ cpufreq-info -f
1862000
# cpufreq-set -g userspace
# cpufreq-set -f 1600000
$ cpufreq-info -p
1600000 1862000 userspace
$ cpufreq-info -f
1862000
$ lsmod | grep cpufreq
cpufreq_conservative 7816 0
cpufreq_ondemand 8464 0
cpufreq_stats 6208 0
cpufreq_userspace 4564 1
cpufreq_powersave 2304 1
acpi_cpufreq 12336 1
freq_table 4640 3 cpufreq_ondemand,cpufreq_stats,acpi_cpufreq
processor 32408 2 thermal,acpi_cpufreq
So everything is loaded. The policy governer is being set, but it seems like it is just being ignored. It doesn't even drop the CPU frequency when I set it manually from the userspace policy.
Does anyone have any idea where I could look to figure out what has changed?
Offline
Hi emphire,
show the output of these commands:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
and see if dmesg command prints some useful informations
Offline
Thanks. It looks like cpufrequtils must have gotten a little more picky about frequencies.
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1862000 1596000
Changing min_freq in /etc/conf.d/cpufreq from "1.6GHz" to "1596000" and max_freq from "1.86GHz" to "1862000" did the trick.
Offline
Pages: 1