commit | 188f1096e8b8bafb03e3b614062dd4d4412d1feb | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 01 09:33:06 2021 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Fri Feb 05 13:38:23 2021 -0600 |
tree | 6636f378b39d311d9f8f53b4f15362e8fc7c5795 | |
parent | a33b2ab1185d0470998860f71fe5d9a8a1c04815 [diff] |
Attn: Refactor dbus calls for pel handling Removed hard-coded system names and instead find system name by dbus object path and interface. Add try/catch handling around dbus calls that could throw exceptions. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I9cfe5fce858ba690fc9a7f0e61a4d249d5a1ef84
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
For a standard OpenBMC release build, you want something like:
meson -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test