Hi all, There have been several reports about systems getting into various trouble after installing lm_sensors these last months. Symptoms could be instant shutdown, beeps, or slowness. Each time, the reason why that "sensors -s" was run at boot time, and the default sensors configuration file would trigger an alarm, and the system would be hardwired to react to that alarm. References: http://bugzilla.kernel.org/show_bug.cgi?id=4332 http://bugzilla.kernel.org/show_bug.cgi?id=5186 https://bugzilla.novell.com/show_bug.cgi?id=160542 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139878 http://lists.lm-sensors.org/pipermail/lm-sensors/2005-March/011369.html And I'm certain I'm missing several other reports on this list and elsewhere. With newer systems featuring hardware protection, I expect to see this kind of problem even more frequently in the next months. It seems reasonable for distributions to run "sensors -s" at boot time, sensors-config itself suggests it. So my conclusion is that the default sensors.conf configuration file should NOT have any "set" line activated. Any such line is likely to create an alarm condition. This is especially true for temperature inputs. Thus I am proposing that we comment out all "set" lines in sensors.conf.eg. What do others think? -- Jean Delvare
