commit | faf33367ce771fbfd1ef58f0b3d395fbd308e8a8 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Feb 16 14:04:51 2022 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 28 13:49:43 2022 +0000 |
tree | 1aa439d323daeef72d966e5a283bf53069574d21 | |
parent | 27a17a5b903d08b48494c2aed8a439503bbce4d7 [diff] |
attn: Moved journal ffdc support into util library Moved the code for collectiong journal entries for event log FFDC data from attention handler to util library. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I62ff1f25407050a013cc5d8d0b0909bbc24500ef
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