October 20, 20241 yr Hello all, I have noticed that whenever I reboot my Orange Pi 5 board, all the 8 cpus slow down to 408 Mhz with no range, as stated by cpufreq-info: Quote root@orangepi5:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.87% (551) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.86% (551) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.86% (551) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 84.0 us. hardware limits: 408 MHz - 1.80 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:75.18%, 600 MHz:2.60%, 816 MHz:0.00%, 1.01 GHz:4.92%, 1.20 GHz:2.63%, 1.42 GHz:2.77%, 1.61 GHz:2.04%, 1.80 GHz:9.86% (551) analyzing CPU 4: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.39%, 600 MHz:5.54%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:2.66%, 1.42 GHz:0.76%, 1.61 GHz:0.57%, 1.80 GHz:0.88%, 2.02 GHz:0.54%, 2.21 GHz:0.34%, 2.26 GHz:3.34% (326) analyzing CPU 5: driver: cpufreq-dt CPUs which run at the same hardware frequency: 4 5 CPUs which need to have their frequency coordinated by software: 4 5 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:85.39%, 600 MHz:5.54%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:2.66%, 1.42 GHz:0.76%, 1.61 GHz:0.57%, 1.80 GHz:0.88%, 2.02 GHz:0.54%, 2.21 GHz:0.34%, 2.26 GHz:3.34% (326) analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:83.38%, 600 MHz:5.82%, 816 MHz:0.03%, 1.01 GHz:0.00%, 1.20 GHz:4.01%, 1.42 GHz:0.74%, 1.61 GHz:0.76%, 1.80 GHz:0.68%, 2.02 GHz:0.76%, 2.21 GHz:0.11%, 2.26 GHz:3.70% (340) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 408 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:83.38%, 600 MHz:5.82%, 816 MHz:0.03%, 1.01 GHz:0.00%, 1.20 GHz:4.01%, 1.42 GHz:0.73%, 1.61 GHz:0.76%, 1.80 GHz:0.68%, 2.02 GHz:0.76%, 2.21 GHz:0.11%, 2.26 GHz:3.70% (340) I have created a cronjob script in order to bring the frequency back to acceptable range. I don't even know if this is the correct way to solve this, but I am running the following: echo performance | sudo tee /sys/devices/platform/dmc/devfreq/dmc/governor cpufreq-set -c 0 -u 1800000 cpufreq-set -c 4 -u 2260000 cpufreq-set -c 6 -u 2300000 cpufreq-set -c 0 -g schedutil cpufreq-set -c 4 -g schedutil cpufreq-set -c 6 -g schedutil However, even though I set the frequency for processors 6 and 7 for 2.30 Ghz using this method, they never go that high, as stated by cpufreq-info: analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:80.22%, 600 MHz:1.90%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:3.98%, 1.42 GHz:2.08%, 1.61 GHz:1.47%, 1.80 GHz:1.01%, 2.02 GHz:1.17%, 2.21 GHz:0.86%, 2.26 GHz:7.30% (2110) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.26 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.26 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.26 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 408 MHz (asserted by call to hardware). cpufreq stats: 408 MHz:80.22%, 600 MHz:1.90%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:3.98%, 1.42 GHz:2.08%, 1.61 GHz:1.47%, 1.80 GHz:1.01%, 2.02 GHz:1.17%, 2.21 GHz:0.86%, 2.26 GHz:7.30% (2110) Those last two processors only go that high if I run sbc-bench one time, than I get the desired speeds: analyzing CPU 6: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.30 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.30 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.30 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 2.30 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.00%, 600 MHz:0.00%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:3.63%, 2.21 GHz:5.86%, 2.30 GHz:90.50% (1538) analyzing CPU 7: driver: cpufreq-dt CPUs which run at the same hardware frequency: 6 7 CPUs which need to have their frequency coordinated by software: 6 7 maximum transition latency: 324 us. hardware limits: 408 MHz - 2.30 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.30 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 2.30 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 2.30 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.00%, 600 MHz:0.00%, 816 MHz:0.00%, 1.01 GHz:0.00%, 1.20 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 2.02 GHz:3.63%, 2.21 GHz:5.86%, 2.30 GHz:90.50% (1538) What is the correct way to solve this? What is sbc-bench doing in order to achieve these frenquencies?? Best regards, Edited October 20, 20241 yr by pdieguez
October 20, 20241 yr Solution Try using armbian-config to set your min/max cpu speeds, or manually edit /etc/default/cpufrequtils
October 20, 20241 yr Author I used armbian-config. Way easier than I expected. Thank you. I did not try that before because it says "deprecated" But anyway, thanks.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.