commit | 86ccc45d33ba1540b047e257c801aca192ae19c8 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 16 13:10:52 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 16 15:20:37 2021 -0600 |
tree | b673e2dfdb29600e545b22f1a1a4fd8948e41d7b | |
parent | bf3326fb84b86edecf8c20b46c548240bda4b980 [diff] |
use proper callout string for next level support procedure Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I23233163e5bc09d1d5b9980c2356349e92ff1794
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