Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / baec7c0145a16b550a9894d0e9b8c290b0847cd4
commitbaec7c0145a16b550a9894d0e9b8c290b0847cd4[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu Mar 17 11:05:20 2022 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu Mar 17 11:05:20 2022 -0500
treee25427e851ae7148e1a103685347f1d7c839bcf8
parentd8b70184f218e5f4bedfc2abeb0278cbdba3fe07 [diff]
Add filter for TI attentions

Generally we will try to find a recovered or unit checkstop attention
that could be blamed as the root cause TI (UEs, cresp errors, etc.).
However, there is a subset of these attentions that will never cause
a TI. So added a filter to ignore specfic bits.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I14ab09eda901c7e82d6bcf52ec8eacb3dd82fffe
1 file changed
tree: e25427e851ae7148e1a103685347f1d7c839bcf8
  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