commit | a7369f86a55ecffc6024d2a6ccd0f53d13d3a2bb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Mon Oct 18 16:52:21 2021 -0500 |
committer | Zane Shelley <zshelle@us.ibm.com> | Mon Oct 18 16:52:21 2021 -0500 |
tree | f3a6f61ef1124fc137baad2e177e1eee30463ee0 | |
parent | 65fefb2c92a358cb3a679f863f1de3fefba18478 [diff] |
Add root cause filters for clock errors Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ia99c31d985e0296b124bfc624b7990d0613dd2d4
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