Hello, while fiddling with my two currently acitve rigs (see below) I’ve observed some strange behaviour:
- On 1 the CPU scaling driver has been set to intel_pstate in passive mode which is to be expected as of Linux 5.8 from Sandy Bridge to Broadwell. The scaling governor is now set to ondemand by default which for some reasons is not Intel’s preferred option but schedutil.
- On 2 the scaling governor is set to conservative by default which isn’t optimal either but maybe okayish for most use cases.
- Setting the scaling governor on 2 to schedutil works most of the time but not when doing this with a oneshot systemd unit on boot. It’s switched back to conservative immediately which is not optimal behaviour.
- Starting the cpupower.service (to set the scaling governor permanently) leads to both 1 and 2 immediately reaching their highest available clock speeds (within their power budget, with 1 boosting and 2 not boosting) and keeping them all the way up. This should not be normal behaviour (I hope).
Are these issues reproducible or has anyone experienced similar behaviour?
1: Core i5 4570S [Intel Haswell]
2: Ryzen 5 3500X [AMD Zen2]