commit | 9a64968497eff44ad83f76d883b50ae6e25c07e7 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Aug 16 09:50:46 2023 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Aug 17 16:07:54 2023 +0000 |
tree | 58d02e142ad3b779e66e92ac6d2bf32e6930136a | |
parent | b28afc99e4444e16357b45366a99f151cb70b17e [diff] |
Updated Odyssey RAS data Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ic9a3300daa44e0e801f240c8514aeaefb4fb9ebf
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