commit | 1d29e5c7da9aad5c3a2ea63a9fa4b5da7c6bd75e | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 17 13:51:02 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Mar 17 13:51:02 2021 -0500 |
tree | ad5ccc6b181bd23886f05ed0b999ae0105e1beff | |
parent | 8af9e46f43d2ffa030275d17716571d4fcc8ad18 [diff] |
Enable OCMB SCOMs in analyzer Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I6fe94c7ee8bf890367a084ced0b6020485dd9cbd
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