|
watch sensors stops reporting fan rpms
I am running Slackware64 14.2 on a supermicro motherboard. I have run sensors-detect and added entries into rc.modules.local that were output post sensors-detect. When I run watch sensors, I have cpu core temps, voltages, fan speeds and a couple of other temps. After a period of time the fan speeds, voltages, other temps zero out and stop reporting. The core temps still work like normal. Any ideas what is causing this?
|
I'm guessing that it stops reporting because of some sort of a default.
Looking at the man page for 'watch' the default runs every 2 seconds. https://linux.die.net/man/1/watch Maybe it zeros out on the fan because of times that the fan stops running? Watch will run until it's interrupted. http://beerpla.net/2007/08/04/watch-...ever-heard-of/ Not sure if the sensors.config file could be adjusted or not to stop the 'default' (just an idea) https://linux.die.net/man/5/sensors.conf Are you getting any time out errors? |
It sounds like it could be an issue with the kernel module used for the sensor chip on the mobo. (The core temp is the sensor on the CPU and uses a different module.)
What module does sensors-detect say you're using? Are there any clues in dmesg when it stops working? |
My sensors-detect finds three different modules.
Code:
coretemp |
Any clues in the dmesg log?
Using sensors with the -u flag might help. Code:
-u Raw output. This mode is suitable for debugging and for post-Here's the cmd for your mobo: Code:
cat /sys/devices/virtual/dmi/id/board_vendor /sys/devices/virtual/dmi/id/board_name /sys/devices/virtual/dmi/id/board_version |
Motherboard
Code:
SupermicroCode:
coretemp-isa-0000 |
Finding out which module that the kernel is using for your fan could be the key. Than you could dmesg the driver.
https://wiki.archlinux.org/index.php/ACPI_modules https://wiki.archlinux.org/index.php/fan_speed_control I don't think Fan Speed Control will help. All 8 read outs (Fan1_min: 709.00 thru Fan8) of the fan appear to be normal with a consistent reading. IF the module wasn't loading you wouldn't get a reading from the sensors cmd at all. So..... I'm baffled as to why it stops reporting fan speeds. I don't know what that 3rd module (w83195) in post #4 is. Never seen it before. I'll look up your board online and that module and see what I can find. Did you install a newer kernel recently? |
I have the following in my /etc/rc.d/rc.modules.local
Code:
/sbin/modprobe coretemp |
I forgot kernel, it is 4.4.14.
|
Quote:
Code:
modprobe w83795Code:
dmesg | grep <name of driver>http://www.supermicro.com/products/m...5500/X8DT3.cfm :idea: Maybe once the module is loads it's interrupted and that's why the reading times out. |
Quote:
If there are any issues with that kernel I'll post it. |
The module was already loaded at boot, but the dmesg did show the following.
Code:
[21813.757157] i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! |
This is the kernel module in question:
https://www.mjmwired.net/kernel/Docu...n/hwmon/w83795 It interacts with the the Super I/O chip (the one that monitors fan speeds and voltages) on the motherboard. Obviously, it stops responding for some reason. You should look at the end of dmesg AFTER it stops responding for clues. |
Oh, I didn't see your post before mine. A quick google shows a very similar error on another SuperMicro board:
http://lm-sensors.lm-sensors.narkive...uestion#post10 I'm not sure what to suggest to you. |
Here's one for the exact mobo:-
http://lm-sensors.lm-sensors.narkive...ol-not-working Thanks, seasons for posting the link to that kernel module.;) --------------------------------------------------------------------------------- What does the end of the dmesg log say? |
| All times are GMT -5. The time now is 02:39 AM. |