commit | 9fb7393efc60449fba06b1cc0f18152abd57c31a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Sep 15 13:34:57 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Sep 15 13:38:27 2020 -0500 |
tree | 49f559d89b152b90501b1ad62329650205b2b3c6 | |
parent | 18db69a9f6d75b958109df0c01876322f7447ade [diff] |
Generate a PEL if any attentions found in hardware analyzer::analyzeHardware() will create a PEL, if any attentions are found in hardware, instead of requiring the caller to create the PEL. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ie5319eca56cbeba4ddc25bcb897d4d143edde742
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