commit | e38a90bd27e737a7abe7f15fbcd4f8a9c78f2f8a | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Mar 02 19:30:35 2022 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Wed Mar 02 19:30:35 2022 -0600 |
tree | 1c152578bcf406705cc03db7195fa2a4dbd5a3e0 | |
parent | a08d1c373269e5d310d9ef0e4752c71e926f4a15 [diff] |
attn: Add dump request timeout The attention handler will wait up to 1 hour for a dump to complete. This avoids a potential endless wait for a dump status change in the case where the dump manager is unable to update the status. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I58ed6b0cbf80a5c3371436165d06a122b0738c66
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