commit | 81d4c89a02fb6a92b511817b440512bea7322cad | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Nov 02 13:43:15 2023 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Nov 02 13:43:15 2023 -0500 |
tree | 701f29975335e3d6126d45a28af7e437b372c50e | |
parent | a4424050a32c269ad324817c71731f7b6e14c8b3 [diff] |
updated RAS data files for P10 chips Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I4d81e7f5101530d848fba83136570aa72ed7dd1d
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