commit | 0cab8ada29d783a1008285ca2166b5af632eaa26 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Jun 04 13:38:33 2025 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Jun 04 14:19:13 2025 -0500 |
tree | 3d820065b46d9ada8106e6acc855cf596342d1d1 | |
parent | 5a58d7c16264a6b18d2844abe61dc3617a8ce590 [diff] |
Add helper func in root cause filter Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: I8a174d6e172ce2e6c0784198f06297fe4f0e3575
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