Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / a16758b7c34b30083bb403c75d6ddea7841ef1a8
commita16758b7c34b30083bb403c75d6ddea7841ef1a8[log] [tgz]
authorBen Tyner <ben.tyner@ibm.com>Tue Dec 07 10:38:05 2021 -0600
committerZane Shelley <zshelle@us.ibm.com>Tue Dec 07 21:25:25 2021 +0000
tree2fb749d6128241e19e2f651e275538e214db078e
parent07ebb9be50d6a449971e4ae36f5fd712a6d09d5a [diff]
attn: Fix no PEL created when TI info unavailable

When handling HB TI where TI info is not available the logic path was
incorrectly handling this event as a TI with EID and no PEL was
being created. This is fixed (a PEL is created) by handling this
event correctly as TI with SRC (SRC == BC801B99).

Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: Icfa2b22c02aa382edec06572e567b2a912e25cf1
2 files changed
tree: 2fb749d6128241e19e2f651e275538e214db078e
  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