commit | b7879d3dae1264b06d8bf0277b5e71e669d30d65 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Dec 06 18:02:03 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 09 14:03:34 2021 -0600 |
tree | 46220761ebd9213ad623fc893b814d61e45af796 | |
parent | ebff0d375ef410eeed34c3ef50bc5745f4def486 [diff] |
Apply resolutions based on analysis type Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I85837e4256d29b88289c377cef99345418b4044c
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