There are three problems: 1) the libsensors4 package does not contain the drivers for certain motherboard sensors. The bug is that It returns an "out of range" error repeatedly (many times per minute) instead of a "no sensors found" error, which ought to trigger completely different behavior vis a vis CPU frequency scaling. This is bug #1: there should be a way to turn this loop off if there are no driver for the hardware. I experienced this on 3 different machines, none of which have drivers for the motherboard sensors.
2) the CPU throttling loop (CPU frequency scaling) is triggered by the aberrant sensor error messages. Fortunately, this is easy to turn off using the debian runtime utility rcconf, where CPU frequency ONDEMAND can be unticked. 3) the frequent kernel error messages being written to the log from the aberrant libsensor errors. This is tricky, as it is not necessarily desirable to prevent errors from being written to the log. it is better to fix the root problems. -- /var/log fills up with "all normal" messages @ about 575/sec fill up the available space https://bugs.launchpad.net/bugs/453444 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
