commit | 7a0dd543c8fef050f7347dde760e6aff84b07122 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Feb 12 09:33:44 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 22 16:50:28 2021 +0000 |
tree | 4d914ee50a4b98f1917861ae9221515583163df6 | |
parent | 6764d70eea47a83adc98c1266dd2f7eb5b7456c8 [diff] |
Attn: Procedure specific error codes in error logs When creating error logs for attention handler failures an error code is presented in the error log. Make these specific to the attention handler procedure that encountered the error. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Ic65343c2cc231ad6340cb5182a1fa75da7c76bcb
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