| commit | 5d835ec9e80934bb998f85c4f495b16553d3d6bd | [log] [tgz] |
|---|---|---|
| author | Ben Tyner <ben.tyner@ibm.com> | Wed Mar 02 20:11:28 2022 -0600 |
| committer | Ben Tyner <ben.tyner@ibm.com> | Wed Mar 02 20:11:28 2022 -0600 |
| tree | 141988a5f8ff35037e277cd9111d93296a4bdc80 | |
| parent | e38a90bd27e737a7abe7f15fbcd4f8a9c78f2f8a [diff] |
attn: Make attn handler restart less restrictive Return back to the default service restart limit behavior which is is a maximum of two failures within 30 seconds before the attention handler is considered failed. This change is needed as it seems that the restart count is incremented for every restart not just the restart after failure. Making the restart more restrictive had the side effect of the attention handler reaching the restart limit if the host was restarted more than two times in 10 minutes even though the attention handler was not restarted due to failure. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I427d60451dce6b613c6e004a063cea5ad06f8fb5
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