commit | 8794bf861a0cdbc6b6e5b9de0029ac91c4c59ccb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Feb 18 15:06:32 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 21 19:36:11 2022 +0000 |
tree | 2bd30658c7896d009b1d35fd48f5661538427480 | |
parent | bc94bdea8543a92d3f41074cd177da78c4028202 [diff] |
ignore CORE_FIR[56:57] in root cause filter These bits simply say an attention came from another core. They should never be a root cause attention. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I98cc80e88a6937035ffd0ddcc6aaa648877b6d84
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