commit | 1a4f0e701a39a43970627190fab7b6a07da3541a | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Mon Nov 07 15:08:01 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Dec 09 19:17:25 2022 +0000 |
tree | 36fa7013a7b953131fd70f6ae8f6954ae4e0534b | |
parent | de22092003c60e9f8d7013fea1ff68ab5afa2a12 [diff] |
Update root cause filtering to use RAS data flags Change-Id: I172540905a39533139821d3cb1676424824bd804 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