commit | 32361f6964916ac215ba93cfe22a4fa48a38894a | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Thu Jul 08 08:20:30 2021 -0500 |
committer | ben.tyner <ben.tyner@ibm.com> | Thu Jul 08 13:30:17 2021 +0000 |
tree | 04568e6bd3e04fb2946f1e35607d5514ddd77183 | |
parent | 324234b4b560ce1d136d96a6950daeb1da1469a5 [diff] |
Attn: Delay start until after CFAM override Avoid potential conflicts between CFAM override DBus target and the attention handler by not starting attention handler before/during CFAM override DBus target start. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: Iba4e5775dbb3b4a5b4aeff5c904c19ffab7b2e04
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