| commit | 7a4652596ba317bf1c0366983ce90b550abebcb7 | [log] [tgz] |
|---|---|---|
| author | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Sep 09 13:53:16 2022 -0500 |
| committer | Caleb N. Palmer <cnpalmer@us.ibm.com> | Wed Sep 14 16:40:35 2022 +0000 |
| tree | 8b0310a7ba95bd59b62f9ff550aa7d3601af056d | |
| parent | 4e4582ba16fd25ea525f85b67ec64e4bd0838862 [diff] |
Add FFDC for signatures stored in scratch registers If analysis was interrupted by a system checkstop there may exist an error signature within two Hostboot scratch regs that indicates the signature from that analysis. This commit adds support to add that signature as FFDC to the PEL if it exists to indicate that a prior analysis was interrupted such that we may be missing a PEL for that signature. Change-Id: I53216e2c7910c69c4e7e74010a5c0045b793bfde Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
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