commit | 8af5685490cc1fe2e3dfa7639ade1bb0307998b3 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Jan 28 15:07:35 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 01 22:01:19 2022 +0000 |
tree | f8582d676ff018caa1ec3c4078fab50a183a3460 | |
parent | 9491cdb459603350d0634c7ed01da39f0269bf76 [diff] |
Clean up default callout in analyzer Using the new ServiceData class functions instead of creating a Resolution to perform the callout. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Id72519c643a0a5b06a19723c0d63b6a789ddd9da
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