commit | dd74a84fa7a80f0452e1f36867ab19ce6680454a | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Nov 02 15:42:34 2022 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Nov 02 16:15:37 2022 -0500 |
tree | ce509d10024f78faf1c6a4839e0e76e7da55c308 | |
parent | e36866c307f565aebe76179fc8f4a7f9684eae50 [diff] |
Update RAS data json with flags for root cause filtering Change-Id: If39f871c3d02c06cb5ad972a361c326ab8391748 Signed-off-by: Caleb Palmer <cnpalmer@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