commit | ff5f9a2dfb9f72dc2d76cf1b50c8f980e8823919 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Nov 19 19:54:12 2020 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Thu Nov 19 19:54:12 2020 -0600 |
tree | b89dd274f58a04083aa8bd572a210a9bbcbc03ac | |
parent | ff76b6b4ab9081d67d1e70d22e3ed5cb52aba758 [diff] |
Attn: Revert back to local FFDC tuple function PEL creation was failing when using the util::transformFFDC. Attention handler was changed back to original code that uses the local function. The util function was not removed. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Iab43155205c44311dba8bb9047b3c37de7e85c80
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