commit | 9bf6804c2d76b92005ad9851cb052d407ea3117f | [log] [tgz] |
---|---|---|
author | Zhikui Ren <zhikui.ren@intel.com> | Thu Aug 13 15:31:26 2020 -0700 |
committer | Zhikui Ren <zhikui.ren@intel.com> | Tue Sep 08 17:18:18 2020 -0700 |
tree | 89b6e8e6f06aafc3f5b8b4dce8733b6860343cd3 | |
parent | f920e09ce4a05265b3d624aca2556579e05d2caf [diff] |
log debug information for sensor threshold assert events There are sightings that TCPUx_P12_PVCCIO_VS_Temp Sensor reports reading of zero and trips the low critical threshold. Add debug prints to gather data. Also add logs for raw value in sensor base class to help debug threshold assert events for other sensori type. Tested: Verified that log messages show up as expected for threshold assert events. There is no unwanted log messages on systems that do not have bad sensor readings. Signed-off-by: Zhikui Ren <zhikui.ren@intel.com> Change-Id: Ib0557e804d275fbb3dce3347b4abec696925cc67
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