commit | 64791cf708574e48182a69e35f39afb40351b1ba | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Feb 15 17:02:37 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Feb 18 17:20:44 2021 +0000 |
tree | 188620cdd6258028b53a03bf7e05923b22026e19 | |
parent | f685afd631a2fe71b6f29ca0ab49b65327399404 [diff] |
Created ServiceData class for hardware analysis This class will contain data for any service actions required during analysis of the hardware errors. Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I93f2c8113881510fff960f7428ee519e8a584938
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