commit | d5fa958419584f1742c67f5276dc534531bfbfe9 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Mon Feb 27 16:12:41 2023 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 01 22:59:58 2023 +0000 |
tree | b0f9973b5fb1a2b7e3d7d2fac32f148769f970b7 | |
parent | 31a8753a468bebdda7c8d190b4341ddaa6ce2034 [diff] |
Add initial RAS data files for Odyssey Change-Id: I70a596dd364057a4ce555546c36cc8369764b785 Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
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