commit | b24b220a3245eb88f02707622d3ee9b19ac79949 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 08 09:06:10 2021 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Wed Feb 10 04:36:11 2021 +0000 |
tree | 0a300173406f3bde67e80f8cdb8225b7afa817f9 | |
parent | d700609cb6dbae60e4698ecf62b92b906f369067 [diff] |
Attn: Provide default TI info for hypervisor TI If TI info is not available for some reason we provide default TI info data so that we can be consistent in our error logging. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ia7768a850400e96904f8bba2a9f9335bef4098be
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