commit | b69b2ba06c626943fc67a5cc7ec77a11d1f4e76b | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Dec 14 13:32:10 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 15 20:01:31 2022 +0000 |
tree | 77696698ef8a872e8251eb6f9385e72ba2543a17 | |
parent | 7c60f4720e5207a5501aec8d24a39acfdb113425 [diff] |
Updated P10 RAS data json with added thresholds Change-Id: Iddc7d587c69560eb8194edf22235b3e9d903412e 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