commit | 5137b2f5a43dbb466805f62971d3bf4105779f9f | [log] [tgz] |
---|---|---|
author | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Nov 12 14:52:31 2024 -0600 |
committer | Caleb Palmer <cnpalmer@us.ibm.com> | Tue Nov 12 14:55:33 2024 -0600 |
tree | f133179ceeb8337a104aa0ea140f0ac2c059a6fa | |
parent | 08f25b219dab3da8bf82170a5c10b19ecf0f3882 [diff] |
RAS Data: Update EQ_L2_FIR[24] to potential checkstop root cause Change-Id: I832170dace507ed7c7af8e54b2ebddaf234d549c Signed-off-by: Caleb Palmer <cnpalmer@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