commit | ebddb4216dc9a435c106b883a116bca8d432dffb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 22 17:17:23 2022 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Mar 22 17:17:23 2022 -0500 |
tree | 0fb680aa846c961e4a9ef523397e5f52e51dc141 | |
parent | baec7c0145a16b550a9894d0e9b8c290b0847cd4 [diff] |
Formatting error in Hostboot scratch reg traces Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I9321e09c53dcd19423aa3e2e33b8be955f1a22d5
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