commit | 0f481a441fa8102602a2e34403e14716324b9e5e | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Oct 19 11:23:43 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Oct 28 17:03:46 2021 +0000 |
tree | 3e0d8fa9e56be66ca36d7b97fdd2253d0610c5dc | |
parent | e550061ea1df23abb6fd175aab4749b3e2e6e3a8 [diff] |
Attn: Properly handle hostboot TI with EID/PLID Terminate events from hostboot with EID/PLID already have a log committed so attention handler does not need to generate a PEL. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I60fa036f7deaaf6dd629f20abde1314d1ff5ecc4
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