commit | 29651ef86a9826108393694ddf3484e9665a9104 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 08 10:51:03 2021 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Wed Feb 10 04:36:17 2021 +0000 |
tree | 6f5be2d6ddccff22bc5cf85382b031f423f1ddcd | |
parent | b24b220a3245eb88f02707622d3ee9b19ac79949 [diff] |
Attn: Add some sanity checking for TI info pointer Add some nullptr checks for TI info. An earlier commit should ensure that this pointer is never null however during debug it proved useful to verify this in a few places. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Idae4a9dd22d61bbac5e76f0a79059efb69981e03
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