commit | feeea83b3fc9aabd23a1ec6d29bd293008954acc | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Tue Apr 06 10:08:11 2021 -0500 |
committer | Ben Tyner <ben.tyner@ibm.com> | Thu Apr 08 11:25:21 2021 -0500 |
tree | b7ecad2521fa61dbf724867a37149791f9e41bb7 | |
parent | 982f172262693198f649d4d8918e5defb1ff6c9c [diff] |
Attn: Add support for raw pel symptom-id Update raw pel symptom-id based on TI info data. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I501938e0fc9dba189999ab1491d23acd15628068
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