| commit | f4792d68505ca033ac01ff42b806d9d7569cf7ff | [log] [tgz] |
|---|---|---|
| author | Zane Shelley <zshelle@us.ibm.com> | Thu Oct 28 18:08:22 2021 -0500 |
| committer | Zane Shelley <zshelle@us.ibm.com> | Mon Nov 01 15:00:34 2021 +0000 |
| tree | efe293fe0ef15779e84c56d483be6309dcaccc00 | |
| parent | 0f481a441fa8102602a2e34403e14716324b9e5e [diff] |
Temporary filtering for checkstop root cause attentions Eventually, we will want the logic to be data driven so that the analyzer can be agnostic to the details. For now this is a simply filtering algorithm to increase the chances we find the root cause attention that triggered the system checkstop. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia0a6d2d64a428e13b37d183ea3b1451080eae727
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