commit | 0bdb60328781da1f0a8344c5a29588adf90bf569 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Jan 09 13:18:01 2024 -0600 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Jan 09 13:18:01 2024 -0600 |
tree | 487aefbbd69dd71fd12182efe76180c05cf66790 | |
parent | 54e71c069311084c5a4a9d09e5f9b6e62a8f41ca [diff] |
Updated Odyssey RAS data files for SRQ_FIR[9,36] Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ifa1f8c4390d39ab0861dd67aa1fd70c9902ae307
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