commit | 869d9bbfbbeed15f25ef120184586192a47eca2a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Aug 05 10:46:47 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Aug 06 14:34:41 2021 -0500 |
tree | f18557aa7eb810f1c5957f458b7cb46552861004 | |
parent | 5191bae9d11562c826c6c1f719815548894def3a [diff] |
Parse and verify the RAS data files When analyzing an attention, the appropriate RAS actions are documented in the RAS data files. Those data files will need to be read and validated against the JSON schema before applying the RAS action. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I127ae1a50bb5b5f4c160ce9fdeaeeb1d041661a0
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