Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 8f07b2e6a2b7b6680cfff380a77cec7667f441e1
commit8f07b2e6a2b7b6680cfff380a77cec7667f441e1[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu Apr 21 15:55:59 2022 -0500
committerZane Shelley <zshelle@us.ibm.com>Thu Apr 21 16:08:05 2022 -0500
treed8aaa753d589c3a1db8b7afdf8edbf9894e1ccf6
parent5dbebde0ac628a62afc0a6a9acb5cc3dd69c5587 [diff]
Add chip at fault to TOD secondary error callout list

The error could be anywhere between the chip at fault and the clock
source chip. So both chips should be added to the callout list.

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