commit | 2b26b2bb7f0482e9d2c5ed3f524f07bcbaa6e1cc | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Dec 15 15:42:02 2022 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Fri Dec 16 13:25:47 2022 +0000 |
tree | faab2fccc4c4a446ec5bd7626beac81ca169e7be | |
parent | 88b100938eddfa2eb3aa6f38500d9984a8f96ba2 [diff] |
Add power fault check to checkstop handler If a power fault is being reported during a checkstop condition we will not call the analyzer. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I9813a55b80eb1b94c6ad2d5cddb2e56b1daa67f4
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