History log of /openbmc/phosphor-fan-presence/hwmon_ffdc.cpp (Results 1 – 3 of 3)
Revision Date Author Comments
# fc2b078a 29-Feb-2024 Patrick Williams <patrick@stwcx.xyz>

hwmon_ffdc: fix compile fail with newer glibc

An upcoming Yocto update reveiled a compile failure due to ignoring the
return value from `pclose` when used as a unique_ptr deleter. Switch
to a lambd

hwmon_ffdc: fix compile fail with newer glibc

An upcoming Yocto update reveiled a compile failure due to ignoring the
return value from `pclose` when used as a unique_ptr deleter. Switch
to a lambda indirection where the return is explicitly ignored.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifa5d3f346f75d37075df78acf916dde8fc1ead69

show more ...


# fbf4703f 17-Jul-2023 Patrick Williams <patrick@stwcx.xyz>

use std::format instead of fmt::format

The std::format is sufficient for the uses in this repository except
for in one file (override_fan_target.cpp, since P2286 isn't supported
by GCC yet). Switch

use std::format instead of fmt::format

The std::format is sufficient for the uses in this repository except
for in one file (override_fan_target.cpp, since P2286 isn't supported
by GCC yet). Switch to std::format whenever possible.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib2576fb530a4d7ce238e1b0bd95b40b476ec2107

show more ...


# bb449c1c 14-Jun-2021 Matt Spinler <spinler@us.ibm.com>

monitor: Shut down if no readings at power on

If there are no tach sensors on D-Bus when the power state changes to
on, then create an event log and shut down the system. This is done
because in th

monitor: Shut down if no readings at power on

If there are no tach sensors on D-Bus when the power state changes to
on, then create an event log and shut down the system. This is done
because in this case the code is not able to know the fan state - if
there are any present or spinning.

The most likely reason there are no sensors (aside from a glaring error
in the config file) is because the fan controller device driver failed
its probe and was unable to detect it, maybe because the device didn't
have power or there was an I2C problem. To aid in root cause analysis
if this were to occur in the field, the code adds the following FFDC
(First Failure Data Capture) to the event log:

* All of the loaded hwmon drivers, taken from /sys/class/hwmon/*/name
* Failure related lines in dmesg, which is where driver errors would
show up.

Tested: Unbound the fan device driver and then powered on the system.
Also disabled I2C to the fan controller device in simulation and tried a
power on.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ic0b80d67ec79c9401f59324fe1134ff12084112a

show more ...