commit | bfa831a88626ec522815c698dc1220f2a3983bc9 | [log] [tgz] |
---|---|---|
author | austinfcui <austinfcui@gmail.com> | Wed Jan 26 15:37:07 2022 -0600 |
committer | austinfcui <austinfcui@gmail.com> | Tue Feb 08 09:25:36 2022 -0600 |
tree | 616fbe9481f504f5185f7b75da57bd1f482deda1 | |
parent | c3fb20620d16997dcd30b964617cd98469de3941 [diff] |
Attention handler trace message refactor Signed-off-by: austinfcui <austinfcui@gmail.com> Change-Id: If86af8fb88b0ce15f6a626676a412a5cee88acc0
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