commit | 18db69a9f6d75b958109df0c01876322f7447ade | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Aug 20 08:23:07 2020 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 24 14:42:34 2020 +0000 |
tree | 26452f471cf9e96ab96bc11c842f4e22db55e7b1 | |
parent | f7ccd8c4ba13dc9d01f9f00183104b6172c87267 [diff] |
ATTN: Removed "... waiting for events ..." trace This trace message seems to confuse people, making them think the attention handler is hung. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Idd1a6f0c07536d989b9982d21930bd87017018d4
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