commit | 51f8202c2c93436c3a1eef951596ebc843651ede | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Feb 22 16:09:09 2023 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 08 16:39:11 2023 +0000 |
tree | b167fdf1cedc0e4bd0ef427366c9c1a9101b51b7 | |
parent | 0577c0137f4d262789bca87f2ba0feac88654011 [diff] |
Update DSTL_FIR callouts in the event of failure to analyze an OCMB Change-Id: I40c17703ad032aa98f02b43d9cb321b7fc86fea3 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