commit | 8f60a621c72bcb134459e4bc5d2cf8b3fa3b41d8 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 01 14:41:30 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Feb 02 16:10:00 2021 -0600 |
tree | d7f41a5b7be3a3d123861d5bb156f6e2be6dab35 | |
parent | b1106b5d0255114f63476825e3ee3864d3318fed [diff] |
Add register capture data FFDC to PEL Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ie6e0dcb0d700ad5d87b0e834bc9880cbe927f28a
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