commit | 1965e504a452e606733d4b2e9504126a393204ba | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Nov 20 10:32:24 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 03 19:36:38 2020 +0000 |
tree | 5617c16b15c8f3710f92f88c8adf503d72dc8264 | |
parent | 7ae9c8c792489587ef44fe945646ec3837492d0a [diff] |
Attn: Additional tracing for attention handler Added some tracing that has proved to be beneficial for debugging recent issues with the pdbg library. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Id4c034a159170439c498129c013d45fbe08cdaa0
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