commit | ff17f96364a2e80d3c804b7cfa87bc07138a8cf1 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Sep 23 08:21:19 2020 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Wed Sep 23 13:55:57 2020 -0500 |
tree | 219292d01cd8ecbed286d9b17a452f7889b1024d | |
parent | 5e622d870609b79b9a210596a42e4a110f210d99 [diff] |
ATTN:ti_handler Conditionally mpipl or quiesce When a TI is encountered the TI handler will check the status of the autoreboot property and either mpipl (autoreboot = true) or quiesce (autoreboot = false) the host. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I9008282aa3acf0ee7d2152cc6c4689d341a9c65d
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