commit | 88c6c6156dbf99fd33da50aad50a96de958215a1 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Oct 05 16:19:28 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Oct 07 16:47:06 2021 +0000 |
tree | 85b64efd49955621ca8c2dd57b0ecc312c695f23 | |
parent | 48f8a4183d6707d6ba0eacb444e5fbc38c940dda [diff] |
RAS data file updates for MCC chiplet Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iaa52b192cf95b86c0748a14c14e09f4ca1d945b1
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