commit | 100c7a266303456fb36bdb07faa77abd1dd6e88c | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Mar 03 16:33:44 2023 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 08 16:41:23 2023 +0000 |
tree | ddb8678dc048c1217b9d9345f29714a7118ac2b0 | |
parent | 51f8202c2c93436c3a1eef951596ebc843651ede [diff] |
Updates to Odyssey RAS data for TP and MEM local FIRs Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ia916f92fe7afc7278c6f8efc2d46ad5223064eb5
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