commit | b83c852aa89e4fd95bcfb370e45c085852a17ecb | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Nov 20 10:45:26 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 03 19:36:38 2020 +0000 |
tree | dbc155f4848d1957fae2f82c60841a6f3abea096 | |
parent | 1965e504a452e606733d4b2e9504126a393204ba [diff] |
Attn: Probe pib target to detect enabled procs Probing the proc fsi target is not reliable for detecting enabled procs. Probing the proc pib target seems to align correctly with enabled procs. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I5b9221c521b70f8045baad3b89f5e8b1635c40ba
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