summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
Diffstat (limited to 'README')
-rw-r--r--README26
1 files changed, 26 insertions, 0 deletions
diff --git a/README b/README
index ffa970fe..30dad320 100644
--- a/README
+++ b/README
@@ -106,6 +106,32 @@ https://amanusk.github.io/s-tui/
for such programs.
+TROUBLESHOOTING
+---------------
+
+lm-sensors is blamed for all kinds of problems on a regular basis.
+While it is always possible that lm-sensors does in fact have a problem,
+almost everytime the problem will be elsewhere. The most likely culprit
+for a problem is one of the kernel drivers prividing data to lm-sensors
+or, rather, the sensors command (and libsensors). If you encounter problems,
+the following tests are recommended.
+
+- Check enabled sensors with the 'sensors' command. Observe and, if there
+ are errors, write down your test steps and report.
+- If any problems are observed while running the 'sensors' command, disable
+ (unload) kernel drivers one after another. After unloading a driver, run
+ the 'sensors' command again and observe if the error is gone. If it is,
+ you found the problematic driver. Record your tests and report to the driver
+ maintainer.
+- If problems are observed while using libsensors from another application,
+ the same procedure applies (though it is recommended to perform the test
+ with the sensors command first). Again, after identifying the offending
+ driver, record and report your results to the driver maintainer.
+- If this does not help, try to run ptrace on the sensors command and/or
+ the application using libsensors. If you find any anormalies, record
+ your results and report.
+
+
OTHER INFORMATION
-----------------