commit | 31a8753a468bebdda7c8d190b4341ddaa6ce2034 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Feb 22 16:16:26 2023 -0600 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Feb 22 16:17:41 2023 -0600 |
tree | 56c949a8d233298a9a328778354fb0178dcf6533 | |
parent | 266096303372e92ce992a8e8074fc1e0b5ab8e82 [diff] |
Update Explorer RAS data json with sorted keys Change-Id: I6ebc92345d2cb857abcbe5b73ca73e3c7a3a5191 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