commit | 171a2e04f8bba716ab5912ac16a4b8b2f3f8b72c | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Nov 13 13:56:13 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Nov 18 02:23:10 2020 +0000 |
tree | 9c0f18dae926e2edb13ad38fa035a4b4e1477771 | |
parent | a029985855c68d3d8a2be9b5924e873f681fcb05 [diff] |
pdbg utils for finding all active chips Change-Id: I444c1062d28c10ecd47426c60ffe0604cc5eaac5 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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