commit | 42684b510c82be54701d7c3ca05335715b8c6268 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Jul 30 16:54:19 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 03 20:05:22 2021 +0000 |
tree | 8ba6565b7569558f8f201b1e5d9f1106590d5494 | |
parent | 8539ee6bd7d9ebf3f8995e827b05001a0b51a1b8 [diff] |
Sync P10 2.0 RAS data to P10 1.0 Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I40df09c9c94dbf6e91b38d469798a4b288c4b90d
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