Eu tive um problema semelhante.
O sistema reportou teimosamente 1.20 GHz - 1.20 GHz:
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.20 GHz - 2.20 GHz
available frequency steps: 2.20 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1.20 GHz and 1.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1.20 GHz.
cpufreq stats: 2.20 GHz:0.78%, 2.20 GHz:64.67%, 2.10 GHz:0.01%, 2.00 GHz:0.01%, 1.90 GHz:0.01%, 1.80 GHz:0.01%, 1.70 GHz:18.33%, 1.60 GHz:0.01%, 1.50 GHz:0.01%, 1.40 GHz:0.02%, 1.30 GHz:0.01%, 1.20 GHz:16.13% (158857)
Mudar o governador não fez diferença:
parallel sudo cpufreq-set -c {} -g performance ::: {0..7}
parallel sudo cpufreq-set -c {} -g ondemand ::: {0..7}
Definir os limites superior e inferior não fez diferença:
parallel sudo cpufreq-set -c {} -u 2200Mhz ::: {0..7}
parallel sudo cpufreq-set -c {} -d 1200Mhz ::: {0..7}
Mas o que fez fez a diferença foi mudar o limite inferior:
parallel sudo cpufreq-set -c {} -d 1300Mhz ::: {0..7}
Então, de repente, tudo funcionou. Eu poderia até definir o limite inferior de volta para 1200MHz.