commit | 1b1915eff34af43e2c6cb5dffc5addbdd705a916 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Oct 23 15:13:38 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 10 21:02:47 2020 +0000 |
tree | f8c206715dfd4d36b25cb8a7912550d26c05c8aa | |
parent | 8c5e4f4e76febcf7699fdc0351553f615354f503 [diff] |
Attn: Add FFDC logs to PEL Gather trace messages from systemd journal and add them as a user data secion to the PEL. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I806915281d9aefd194f90e752c27a89ad375fb13
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