commit | a9b443442d16f836c08931e1b53deb5a1784d692 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Sun Aug 08 17:15:52 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Sun Aug 08 17:15:52 2021 -0500 |
tree | d13c941d22b9e3be3bf226005154042d541bb475 | |
parent | 869d9bbfbbeed15f25ef120184586192a47eca2a [diff] |
Move RAS data support to RasDataParser class Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ib6d604504cce4564c36fb2b461eb330e97811ee6
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