commit | c1e1c00068b08fdeb613774af391a6c2308f82e8 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Wed Feb 16 15:09:31 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 28 22:10:18 2022 +0000 |
tree | a23614830db3f59efd7c564b54b1f74660059460 | |
parent | 1315968c4aa294f2e4b414fffb8cb012578fa878 [diff] |
analyzer: Modify create pel to use util Modified analyzer create pel to use the util library base create pel functionality. The specific pel content collection and creation remains in the analyzer create pel function. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I5529431fc649e741e52cc093f33806797da35e76
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