commit | 34b0ce19b894e4e1b56d33134898a5919d8e2e48 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Mar 26 14:04:59 2025 -0500 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Wed Mar 26 14:05:46 2025 -0500 |
tree | 4891d9aa31792c7d03b0cd0774f2fa7eed1531c4 | |
parent | 4d8bb504380c51fbc5c2ddf6871c74aff2df01a1 [diff] |
Filter out attn_from_ocmb FIR bits during TI analysis Change-Id: I310abaa2b04eef7f13c8835da69eb2ac6df45f25 Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
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