commit | d8b70184f218e5f4bedfc2abeb0278cbdba3fe07 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Mar 10 10:50:22 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Mar 11 15:24:25 2022 -0600 |
tree | b1f8a821ec7da36e53bc91e17c00bc2a198881a9 | |
parent | c49d20b960b385ec641bd57ca5c1946b55ff2ea6 [diff] |
Add SUE service procdure callouts Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I1e5f3fbdfb93eb69c6e3c8f0b79721b6dd5f0dbe
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