Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 76e52f6d8808e15f44c84a28e623cfed89654b5d
commit76e52f6d8808e15f44c84a28e623cfed89654b5d[log] [tgz]
authorBen Tyner <ben.tyner@ibm.com>Tue Feb 01 10:46:44 2022 -0600
committerZane Shelley <zshelle@us.ibm.com>Thu Feb 03 19:33:30 2022 +0000
tree9120acb632e2d1bfd9d04516df166c6836224ea2
parent475237a48208f4ebcd0dd6aed32721fa16c2f352 [diff]
attn: Collect SBE FFDC on getTiInfo chip-op fail

If the PHAL library throws an exception during the call to
getTiInfo it may provide some SBE FFDC data which the attention
handler will collect and put into an event log entry.

Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: I834719944ed646ab6478f554965cf976a7c606e0
4 files changed
tree: 9120acb632e2d1bfd9d04516df166c6836224ea2
  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