The system is working great, fans are around 1000 rpm on normal load when the system is in use:
inxi -s
Sensors:
System Temperatures: cpu: 61.9 C mobo: 48.9 C
Fan Speeds (rpm): fan-1: 1083 fan-2: 1081
GPU: device: amdgpu temp: N/A device: amdgpu temp: 38.0 C fan: 0
However, when I manually lock the system or wait for the screen lock/blanking to kick in, the fans speed up and stay there until the screen is unlocked again. Here the output of inxi right after unlocking the laptop:
inxi -s
Sensors:
System Temperatures: cpu: 60.9 C mobo: 42.9 C
Fan Speeds (rpm): fan-1: 2708 fan-2: 2593
GPU: device: amdgpu temp: 30.0 C fan: 0 device: amdgpu temp: N/A
As you can see, no change in temperature, but the fan speeds more than double.
Any idea what causes this?
Is KDE/Plasma actively controlling the fan speed and stops doing that when locked? To my knowledge there is now a kernel module that takes care of fans and overheating, right? It has been years since I had to actively do anything about that on linux, using lm_sensors I remember, so I thought that was not necessary anymore?
Thanks for the tip. I did check baloo, it says indexing is done - and also completely halting it before locking the machine does not help.
It is a single-user laptop btw, rolling release, updated today.
Logging the process activity while locked also suggests it is not any actual CPU activity that leads to increased fan speed. And the general journal log also gives no clues. The increased fan speed also starts immediately after the login screen disappears from the lock screen and continues unchanged until successfully logging back in. Moving the mouse or keyboard inputs do not affect it, screen blank or not does not affect it.
Is there a subsystem that I can tell to increase logging verbosity or something like that to get some more info on what is influencing the fan speed?
I was having power draw and resource usage issues on Plasma 6.2, fans ran high all the time. I just recently updated to 6.3 and it seems to have dialed back to a more reasonable amount of computing.
This fits, and while unresolved there are workarounds like switching to a console tty (Ctrl-Alt-F1) while the screen is locked or triggering a restart of kwin_x11 once during a session with systemctl --user restart plasma-kwin_x11.service
Hopefully, once upgraded to 6.3, I won’t have to do that anymore.