commit | ebff0d375ef410eeed34c3ef50bc5745f4def486 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Sun Nov 21 10:52:07 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Dec 08 17:52:01 2021 +0000 |
tree | 379c1e28cb94d9f69e534871a8211b7c64f5d9d0 | |
parent | 6a62e40dc7cfe649a5dd3209097f3ec6fd93f4e4 [diff] |
add analysis type to analyzer main function The analyzer behavior will vary depending on the type of event that triggered analysis. For example, we do not want to perform any service actions when manual analysis is done from the command line. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iecfbac7f680b3fefebb0e02a9caa5fc06b692c7a
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