commit | b83355686bc23400c5cf7988e0570fd13da20777 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Jul 16 12:43:52 2021 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Tue Jul 20 14:30:49 2021 -0500 |
tree | 23ba11dee022921fc5810698a01e5eb7f3936b1a | |
parent | 32361f6964916ac215ba93cfe22a4fa48a38894a [diff] |
Attn: Do not always trace hostboot registers Only trace hostboot registers if we are handling a checkstop or TI. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I66f234b424dbd36e8789c64c9a9e82a3a0e75d44
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