Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / a4424050a32c269ad324817c71731f7b6e14c8b3
commita4424050a32c269ad324817c71731f7b6e14c8b3[log] [tgz]
authorCaleb Palmer <cnpalmer@us.ibm.com>Tue Oct 24 14:42:06 2023 -0500
committerCaleb Palmer <cnpalmer@us.ibm.com>Tue Oct 24 14:48:06 2023 -0500
tree483d434f6d44e9e4d9ca660162faf0c8ab44308e
parent7435fc0eb526cf12e56291202d12ddb4b5f5a590 [diff]
Add root cause filtering for RDF_FIR bit 16 and 41

RDF_FIR bit 41 can cause bit 16 as a side effect,
therefore, this adds some special filtering to
blame bit 41 if both bits are found set.

Change-Id: I4f3bf4f12315923ac810e404a1066d4d09c7525f
Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
1 file changed
tree: 483d434f6d44e9e4d9ca660162faf0c8ab44308e
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .eslintignore
  8. .gitignore
  9. .prettierignore
  10. .prettierrc.yaml
  11. buildinfo.hpp.in
  12. cli.cpp
  13. cli.hpp
  14. config.h.in
  15. LICENSE
  16. listener.cpp
  17. listener.hpp
  18. main.cpp
  19. main_nl.cpp
  20. meson.build
  21. meson.options
  22. OWNERS
  23. 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