commit | 8af9e46f43d2ffa030275d17716571d4fcc8ad18 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 11 10:44:28 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 11 17:48:44 2021 +0000 |
tree | 26e9a620efd73ac55b9b8a8bfcb5cba130e40ec4 | |
parent | 5f6e3deb694c0d8f4d5fa87517fdc9c260961e2b [diff] |
Move root cause signature into service data object This allows the analysis code to access the signature from the service data object instead of passing around two variables in all of those functions. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ib85386759068aee26dc1e8b9e8d609daf7e63c1b
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