commit | d3b9bac9e8be6c2989aadc65c6236c9ce1f189ec | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Nov 17 21:59:12 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Nov 30 08:34:22 2020 -0600 |
tree | 48c2687b702a1994bb756b783a36c3aa8afb8ea2 | |
parent | ff5f9a2dfb9f72dc2d76cf1b50c8f980e8823919 [diff] |
Expanded PEL support for analyzer logs Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ie33c5b777d537ab054a06c09087edcddcc129f15
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