commit | ec227c2cf954772403f0a685cb9b600f40ba2c5a | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 09 15:54:40 2021 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 09 15:54:40 2021 -0600 |
tree | a25d9dafbf7ccb5ad05695d5e7044b268b370977 | |
parent | f17bf3e5db12ad1885b1f6d72a0b54a0a86b9b2d [diff] |
change root cause filter based on analysis type Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I60ad9fc7ce03fb4525de54c9e0f651a28a95885b
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