commit | 7cebfbc60b07384c8a17cc0fcef4415315ad8d04 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Oct 21 16:13:43 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Oct 21 16:13:43 2021 -0500 |
tree | 90b421dd1dd24efd7728687806e4f6a2a2c439e9 | |
parent | a7369f86a55ecffc6024d2a6ccd0f53d13d3a2bb [diff] |
Fix syntax errors in ras-data-schema-v01.json Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iff0d16c01efc2c6c366c7a1bb0968f6ccfeb50ca
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