commit | 216ff9f1e5b1563c571aa41ff7412420d00a0c01 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Mar 26 14:52:26 2024 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Mar 26 15:44:28 2024 -0500 |
tree | e93583b869b7401062adedbd363b31e4d1c6ebfc | |
parent | 60cb2e4277759661f9054d263cc877dc7fa406ed [diff] |
Fix TI level 2 callout to use FFDCFormat::JSON instead of Custom Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ia8f59f69a4e1fa76d38e6eed00cc3da9cc609d2e
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