commit | 27a17a5b903d08b48494c2aed8a439503bbce4d7 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 21 20:33:49 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 24 13:59:17 2022 -0600 |
tree | 651e6025f2e862b00227a8456fe46d7c532a38aa | |
parent | c7026261bb05cc509b0c7fb204ba967419a8b35d [diff] |
Hardware analysis support of TOD failures Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I8e2659cc832113e05c99b8dd091757bcab3dcdea
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