commit | ecde53fc6002709e52cfec55347b802a91614f23 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Dec 13 15:11:47 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 15 20:03:55 2022 +0000 |
tree | f74366e04b89812f367ac023d20ebcad7bd0e787 | |
parent | b69b2ba06c626943fc67a5cc7ec77a11d1f4e76b [diff] |
Adjust TI root cause filter to skip INT_CQ_FIR[47:50] These bits are recoverable errors and should not be blamed as the root cause of a TI. Change-Id: I666eadbde0c2a0935fa47206f337112bc44a100f 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