commit | 4bbcb38f367e58b3724768ad998e31610b38869a | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 22 09:29:00 2021 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 22 11:22:11 2021 -0600 |
tree | 820393f755cb8c323791a9a315771ff5191533b1 | |
parent | 7a0dd543c8fef050f7347dde760e6aff84b07122 [diff] |
Attn: Determine TI source by host running state In cases where the TI info is not available use the host running state to make an educated guess as to the source of the TI. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I95c59ecad90b3aec417a64df4eac0ac5cb50dc09
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