commit | 90d125241e01583c37365c6394b537835b3f328d | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Jul 20 13:20:10 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Jul 30 19:01:23 2021 +0000 |
tree | 1d45622504d5bb87aacf95e327e3b440e56ee080 | |
parent | 659e65cf16807f701ad82edc37fb50e4af984ced [diff] |
RAS Data file definition and JSON schema Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia1a2b2e6470f0b02271920c999d51ee897d4bf9d
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