commit | e90b85dc659b2a8224fd6a52110460e36277ba6d | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Dec 17 17:24:49 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 19 14:33:25 2022 -0600 |
tree | 3ac39aaa6c88de4a524f2d2e30f3db19bf45a4b7 | |
parent | 2c228cdcfbf08b0b997403a2cfa13c27c247a736 [diff] |
plugin for LPC timeout callouts Change-Id: I39fed3c1ba5a16283c33c5072479f24c9c69a208 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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