Hi, On 2022-03-05 18:21, Armin Wolf wrote: > Package: lm-sensors > Version: 1:3.6.0-7 > Severity: normal > > In lm-sensors.service, the sensors program is executed twice. > The second execution happens without the -s flag, causing > sensors to read all sensors and print the results to the > system log.
Yes, the second call is actually done on purpose due to the way the alarms work. The "sensors -s" sets the minimum and maximum limits, however the ALARM flags are still latched until the next time the sensors values are read. This is the purpose of the "sensors" call just after, in other words it makes sure to clear the ALARM flags that might have been triggered by different limits. See /usr/share/doc/lm-sensors/README.Debian.gz to see how the ALARM flags work. > On a Dell Inspiron 3505 however, this results in a freeze for > ~4 seconds during boot, caused by the second (and pointless) > execution of sensors coupled with very slow sensor reads. As said above the second call to sensors is not pointless. The bug is actually on the kernel module side. You should get it fixed instead, and in the meantime you can probably blacklist the module. > In order to fix this issue, the second (and pointless) execution > of sensors should be omited. Not it shouldn't as it is not pointless. The kernel should be fixed instead. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
