commit | 2d114321d95e6d49ee152df3a941d0662bd44315 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Aug 25 17:06:12 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Aug 26 16:18:56 2021 +0000 |
tree | 35059c9ac961de2191294a98ccd42c5d7d392574 | |
parent | 9513582b8748fe2566ff451c2a2514e079dd56fb [diff] |
Support for callout list FFDC The FFDC contains relevent fields to a callout that otherwise would not be displayed in the callout user data section. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iadb71587b7219c4d352fa583ddd86f290de4a747
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