commit | 584f179eaeb2ab3ad8fc9725666b4d1b33594473 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 17 10:04:08 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 18 02:23:10 2020 +0000 |
tree | cdaf30ece1dbe3392878c5b4d9ed39461b783052 | |
parent | 171a2e04f8bba716ab5912ac16a4b8b2f3f8b72c [diff] |
utility to transform an FFDCFile list for PEL consumption Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Iae1bc8ed1a1eea9f9d7593e59c21a861a8236a34
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