commit | 86aa97a50808e8358ac8582e2240c6ae50dd2ff1 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Sun Dec 12 21:29:16 2021 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Sun Dec 12 21:54:17 2021 -0600 |
tree | 718e6fd9dfedf8de24daceee8dfd0bb10aa01f39 | |
parent | ec227c2cf954772403f0a685cb9b600f40ba2c5a [diff] |
attn: Always request a dump for TI with SRC Attention handler should only honor the TI info hostboot dump flag for TI with EID. For TI with SRC case always request a dump. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I5580d1f941dfaecd4211fc770d9d2b52cd2f2c75
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