commit | 7029e525adf8786bf374a51599a8938d6a8a3e48 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Aug 09 19:18:24 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 17 20:05:36 2021 +0000 |
tree | 9010b5a8af640bc3ac2bb7ade593dbac6a8cc6a7 | |
parent | fe2c50d70c366f2454c30bfec3e22f53243a00bb [diff] |
On checkstop request dump and transition host After checkstop analyses completes attention handler will request a dump and the transition the host. The type of dump requested is dependent on the results of the isolator. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I1116be8f8d045a4916d3321f461c22345fecf274
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