commit | c7a0a0c5dcfc1d4de6abd4816f88315cacbd0de1 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Jul 26 15:01:50 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Fri Jul 30 19:01:23 2021 +0000 |
tree | c2a905fcfc6de3719e82ffe968808a87c7e0b5ed | |
parent | acd516bfd20318088e9194d76d961a1dd2bfa977 [diff] |
Initial RAS data files for P10 1.0 and 2.0 Initially, all bits are assumed masked. Updates will be make later as reviews are done on the chip data files. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I87deca4032abcb7a4fd1096b9ba9257df4d8b9dd
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