commit | 5adc96eed9197c08bfaf66b4e204b3d519917f08 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Nov 20 10:54:12 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Thu Dec 03 19:38:42 2020 +0000 |
tree | 953b68ce780ae26cbed96c9791958d2ca572f8be | |
parent | b83c852aa89e4fd95bcfb370e45c085852a17ecb [diff] |
Atn: Add sanity check for invalid fsi reads We recently saw traces where fsi reads were reporting values that seemed to be duplicates of the last known good read. Added a sanity check that will indicate whether this occurs due to a pdbg library issue or a sbe fifo issue. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I56888f1cdb66650915ad1b2b350b5cd22861ef76
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