commit | f7ccd8c4ba13dc9d01f9f00183104b6172c87267 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Aug 19 19:17:02 2020 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Fri Aug 21 10:24:04 2020 -0500 |
tree | 731ef7e87ed8fd972012aaa09a1d4eb4b3ee7261 | |
parent | 98430b3033c72ce8c293aa0b7d51a7ea8b94464b [diff] |
ATTN: Start attention handler AFTER fsi scan Load the attention handler after the fsi scan and stop the attention handler when the host stops. This to make sure the attention handler is able to successfully read cfam data using the libpdbg library. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ia710e0ff29c81bae172ddf7aed06d4014aafc793
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