commit | 4d8bb504380c51fbc5c2ddf6871c74aff2df01a1 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Fri Mar 21 15:46:38 2025 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Mar 25 09:57:34 2025 -0500 |
tree | c533e4930da5302a049b8b10449883930f1c6f3f | |
parent | 2cee29db08ad57df3df974fc2aee7e73f938a935 [diff] |
Add new check for simultaneous chnl timeouts Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: I03ede43980d5fd85501582097e0812f5332c9752
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