| commit | 3453354b838885bfe47754bdf116ecedde87116d | [log] [tgz] |
|---|---|---|
| author | Paul Fertser <fercerpav@gmail.com> | Tue Jul 20 08:29:09 2021 +0000 |
| committer | Ed Tanous <ed@tanous.net> | Tue Jul 20 15:34:31 2021 +0000 |
| tree | d0a7d09d549bf37492acb032061247272c83feac | |
| parent | 585d3a079d00382b1996740e78075867c03db3c7 [diff] |
PSUSensor: improve error logging PSU sub-events might be asserted by to different alarm flags as returned by the kernel so when debugging a hardware or driver issue it's important to know what condition exactly triggered. Same about errors reading data from PMBUS sensors, for debugging it's essential to learn precisely what happened. Example output: System error 11 (Resource temporarily unavailable) reading from /sys/class/hwmon/hwmon12/temp1_input, line: 199 PSUSubEvent asserted by /sys/class/hwmon/hwmon10/curr3_crit_alarm PSUSubEvent asserted by /sys/class/hwmon/hwmon12/curr3_crit_alarm System error 6 (No such device or address) reading from /sys/class/hwmon/hwmon8/curr3_input, line: 199 PSUSubEvent asserted by /sys/class/hwmon/hwmon15/curr3_crit_alarm Monitoring with strace confirms psusensor happily continues to read from the file descriptors in question after the glitches. Signed-off-by: Paul Fertser <fercerpav@gmail.com> Change-Id: I2f1adac52ad8393d455c3c1a04e7f9bac479f68f
dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.
runtime re-configurable from d-bus (entity-manager or the like)
isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible
async single-threaded: uses sdbusplus/asio bindings
multiple data inputs: hwmon, d-bus, direct driver access