commit | 979e2871f3fd78cf68ba9e2c325c2ae784a7d8b4 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:46:06 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Sep 20 22:46:06 2021 -0500 |
tree | 6b4b6d470a28c0e227cc5f999b0fe7a05ba3fa8a | |
parent | 5d63cefcada92a8588ab55fb2a741c898cb19a8b [diff] |
Prevent duplicate entries in callout list If duplicates exist, only the highest priority callout will remain in the list. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ibec768b22c944965460010be8867749a8c0f9044
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