commit | 65fefb2c92a358cb3a679f863f1de3fefba18478 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Oct 18 15:35:26 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Oct 18 15:35:26 2021 -0500 |
tree | 7fc91fbac10ea833c6e159d917f4bd00878a654e | |
parent | ceb08b2b7dd1ae3b0ef791c432a2095f376f3594 [diff] |
Move root cause filter support to separate source file Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I73527c672bab5bd33ec48cf6d07a1cc7d746faa3
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