commit | d57d6ccd24699f8b1a288d65d36d671fb868ffb9 | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Feb 11 13:28:08 2025 -0600 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Feb 11 13:28:08 2025 -0600 |
tree | 7f2d788fb60d05799112d76e5ebdcc054ddc13fe | |
parent | 588ca2b8cdecd8b28ae840cbd9a2ed7a0bdabdd2 [diff] |
RAS Data: Fix Odyssey dimm1 metadata Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com> Change-Id: Ib043da5603b9294f21823a15fe7e6a6a465136a9
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