commit | ff068a154e5811bbddead76cc0e004cbf88870ac | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Jun 17 17:45:40 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Jun 17 21:10:11 2021 -0500 |
tree | c5cfe91c77aa4ea3e9251f7e887b24c24a67e43a | |
parent | 6bc43c9b896724c27317ac50a88e5ddaa2882484 [diff] |
add node position to signatures and register list Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Id21cc5e48eb699161e2f2ba8d23b42c1c860a49b
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