Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / fc7e24767fe60e3087eb5e1f1325ff15bb48b97e
commitfc7e24767fe60e3087eb5e1f1325ff15bb48b97e[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Fri Jun 24 14:58:41 2022 -0500
committerZane Shelley <zshelle@us.ibm.com>Mon Jun 27 10:40:31 2022 -0500
tree84227eec3afd8a3f73e66220e072aa1ffa00e126
parentb82cbf75828ae5f6f4cbfbf3c15adec33550fe38 [diff]
CORE_FIR recoverables could be blamed as checkstop root cause

If a CORE_FIR recoverable attention fails recovery, it will trigger a
core unit checkstop attention via another bit. All core unit checkstop
attentions have the potential to trigger a system checkstop attention.
Therefore, all CORE_FIR recoverable attentions could be blamed a system
checkstop root cause attentions.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: Ib2f3916218b4dce88797f645a302716ef4fd4d49
1 file changed
tree: 84227eec3afd8a3f73e66220e072aa1ffa00e126
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .eslintignore
  8. .gitignore
  9. buildinfo.hpp.in
  10. cli.cpp
  11. cli.hpp
  12. config.h.in
  13. LICENSE
  14. listener.cpp
  15. listener.hpp
  16. main.cpp
  17. main_nl.cpp
  18. MAINTAINERS
  19. meson.build
  20. meson_options.txt
  21. OWNERS
  22. README.md
README.md

Hardware Diagnostics for POWER Systems

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.

Building

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