commit | 038f48a320e570a6e2778f46f4de3da8211dd677 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Jan 11 13:44:57 2024 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Jan 11 13:50:43 2024 -0600 |
tree | 768b37247f2f7f27a2db52f0e632203da0962d08 | |
parent | 0bdb60328781da1f0a8344c5a29588adf90bf569 [diff] |
update handling of OCC SRAM ECC errors Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I43d993c89eb33179e4194ee74dfb9b9f52ce37ca
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