We switched to the interactive cpufreq governor a while ago which should act a lot more fine grained ... could someone check if the issue still exists with a recent image
We switched to the interactive cpufreq governor a while ago which should act a lot more fine grained ... could someone check if the issue still exists with a recent image