commit | 934635e04c6732db087771a1407fed1511edf556 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Thu Nov 03 14:34:16 2022 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Thu Nov 17 10:37:47 2022 -0600 |
tree | d84ab924d1334a01add0d1c42983c1eba582c2f2 | |
parent | f1184392e77da220d603e764eadbe946d6ddfe11 [diff] |
Update Explorer RAS data json to auto-generated v2 Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: I0b5062f3f8dac85d9f8abfe2115c15aae3e12d0c
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