commit | b6401edf97b29db6662c64c735d495222abbe4a0 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Jan 11 09:08:07 2021 -0600 |
committer | ben.tyner <ben.tyner@ibm.com> | Fri Feb 05 18:51:25 2021 +0000 |
tree | d1b23ba8558f6b6ff1849debb552dfa09d4361e9 | |
parent | 8f60a621c72bcb134459e4bc5d2cf8b3fa3b41d8 [diff] |
Attn: Add TI info additional data to pel ffdc Some TI events provide additional data (up to 944 bytes) beyond the base 80 bytes of standardized data. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Iefdf7c1b57575bc7d8692893ad9693d346674956
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