commit | a9f85590e8e39f1a66f0160d8ac63910c030d0af | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Jun 28 18:28:12 2022 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Fri Jul 08 10:45:41 2022 -0500 |
tree | 4d59b64d8a81d9aa4801745c30e6692b02760155 | |
parent | fc7e24767fe60e3087eb5e1f1325ff15bb48b97e [diff] |
Attention handler configuration file support The default behavior of the attention handler can be overriden by modifying the config file contents. The behavior can also be defined by the associated build option. The default behavior remains unchanged. The intent of this change is to allow other components to change the attention handler behavior by updating the configuration file and restarting the attention handler service. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I8f73004c926a3a070c5feb690ee5684429f922c5
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