commit | fb1905453908a6cfe0136bcf39b818e7e8ece225 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Nov 06 09:27:56 2020 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Mon Nov 16 14:10:16 2020 -0600 |
tree | 07035669e82aad910b50d23f33ff860223a25a42 | |
parent | 1c4b02ea682b62a74bc28986c574774755d6cdaf [diff] |
Attn: Cleanup trace messages Cleanup attention handler debug trace messages. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I2d5cc50e88c42278a37742ee361aec557ee15b28
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