commit | 2fbd267eaef235b61ddec84fae7ed26b9398c7f2 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 03 13:56:35 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 08 21:08:31 2022 +0000 |
tree | 26e5488f76bf626cf2cd291bc91a95337a69cc57 | |
parent | bfa831a88626ec522815c698dc1220f2a3983bc9 [diff] |
Better exception handling in the analyzer Give the ability to continue creating a PEL with FFDC if there is an exception in the analysis portion of the analyzer. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I2de281a7c974cfc80779a861a12cb2b9c99e0491
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