Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 026e5a3fee904d9ff41fe89e8ceb134c09aebaf0
commit026e5a3fee904d9ff41fe89e8ceb134c09aebaf0[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu May 05 10:37:59 2022 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu May 05 16:05:14 2022 -0500
tree10519ff612a131abe6248e16162586f984aac36f
parentd28d5f8b6d6a6122a06c285b6841ba2a46d9267f [diff]
Avoid guarding on TOD interfaces errors

The error could be anywhere between the two processors in the interface.
Fatally guarding the MDMT will cause system outage until service is
done. Instead, do not guard on the TOD interface errors to avoid outage.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I446917bad985e5143657398b2fbadacf6e8c4a9d
2 files changed
tree: 10519ff612a131abe6248e16162586f984aac36f
  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