[FS#910] Raspberry Pi 3 keeps attempting to change CPU frequency and failing

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#910 - Raspberry Pi 3 keeps attempting to change CPU frequency and failing
User who did this - Chuck (nathhad)

----------
Digging up this older bug report to leave a partial solution that may be useful to others, but this is still an active issue for me with Raspberry Pi 3 Model B Rev 1.2 running GoldenOrb_2020-05-16 (OpenWrt 18.06.7).

I've seen in other places on Raspberry Pi references that this tends to be tied to something related to USB.  For whatever reason, eliminating CPU frequency switching by any of several possible means does solve the problem.  You can either set the frequency manually to a single frequency in /boot/config.txt, or (as I've chosen to do) you can change the governor after boot using /etc/rc.local to one of the two governors that only uses a single frequency (either performance or powersave).  In my case, I've locked mine to powersave, since my Pi is rarely heavily loaded.

In /etc/rc.local, add the line:
echo powersave > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor

Or, of course, use performance if you need full speed.

If you need something in between, it's relatively easy to set a fixed frequency anywhere from 100 to 1200 (on the 3B) in config.txt, as well, and there is ample info on how to do that on the Pi forums (including tons of fairly advanced info in the Advanced users > Overclocking thread, which is 46 pages long and includes participation from one of the main board engineers for the Pi).
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=910#comment8656

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.