commit | 5c5db65a37d953cb9393f257aab90a0a209d4861 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Mon Feb 22 18:22:35 2021 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Tue May 11 16:41:26 2021 -0500 |
tree | c2e3f43d7e2b04c10afc15adeaef9197c2170dd5 | |
parent | 832526df90ead77f5dcb501406cb07fbbfa7046b [diff] |
Attn: Dump request and monitoring support Support for requesting a dump from the dump manager and monitoring the dump progress. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I03acd2b8c13ce0b5ced63ff7fbb32f7225467aee
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