commit | 7698b304a6e778c15f73f724bb8e05f18e3052e8 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Aug 09 16:00:03 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Aug 10 22:17:01 2021 -0500 |
tree | fd4af878e97438184a0f44b7cd3f7bd0e4cbaf2e | |
parent | 2f92130c7964a286a1e76df938e36bc21ad8033d [diff] |
support to parse RAS data signatures and actions Change-Id: I114e62f11f962fa9f5b1d7cf52219984e5800f86 Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
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