commit | f17bf3e5db12ad1885b1f6d72a0b54a0a86b9b2d | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 07 13:16:37 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 09 14:03:34 2021 -0600 |
tree | 5163574c1e267ae2084b26bd34b6ca8e6aa37757 | |
parent | 82be3ab53ec05be6f225aef6fb25713de50fd349 [diff] |
Add informational PEL for manual analysis Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Id64b7a47749a1b32008ddead947cee46eeca4a6d
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