commit | cbd20fa3ef069f5b34013d177a5468e37a83b77e | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Fri Jan 21 17:24:41 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 26 09:59:52 2022 -0600 |
tree | f1b27c375447a5eeca5ea10f7bf9a4bc257c8870 | |
parent | 35257fd2fbaea4562cdd937ad60b1d8a4c9ed9af [diff] |
RAS Data File updates for TOD fault errors Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I1b1e1a7690e294ab2569d0fad60fa215acc37479
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