commit | 9c69e3716305aa8ba61b1d558879cc4b46f2f7b6 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Oct 17 15:48:11 2023 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Oct 17 15:49:28 2023 -0500 |
tree | 5f0183ea06f490c0de870bd970d30d8a5ac5106f | |
parent | c3038c033f621c2b52d75a625c68040bde77fb3b [diff] |
Update Odyssey RAS data json with latest changes Change-Id: I51933e440a110a2cd87f00438d93d2e3e4f49b31 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