Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 44d6f25ff8eb175afe5a29dd7986f2c98c73e499
commit44d6f25ff8eb175afe5a29dd7986f2c98c73e499[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Fri Oct 18 15:12:19 2024 -0500
committerZane Shelley <zshelle@us.ibm.com>Fri Oct 18 15:40:50 2024 -0500
treeb56b8fa24c1ea5541a7d07a7214e8c79c9d6ca2e
parenta0c724d3d425032213dbd48247d93cc76d61a331 [diff]
Add more debug data on Hostboot TI with EID

On this path we don't create a log with FFDC because we assume Hostboot
has created the correct log. Adding more traces to the journal for
debug.

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