commit | 74b40bf0499cc53c1b129971785a8c7dfcde8b56 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Sep 15 19:37:04 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Sat Sep 18 22:29:12 2021 +0000 |
tree | 48c5c81c7f15d10f4cd8bc4ceac7245113171de2 | |
parent | 4e3faa232a0cb7aa222e84c21b4692dc9840603c [diff] |
Attn: No event log entry for hostboot FFDC error If errors are encountered when collecting hostboot FFDC then just trace the error since we are already in a error path and an event log will be created. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ie6564fe1840ffa3fcbeca35ee2463dc9b52cf833
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