Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 329dbbde96a1d73d96b87fd03d53561ba8899f1e
commit329dbbde96a1d73d96b87fd03d53561ba8899f1e[log] [tgz]
authorCaleb Palmer <cnpalmer@us.ibm.com>Mon Oct 03 15:05:43 2022 -0500
committerCaleb Palmer <cnpalmer@us.ibm.com>Mon Oct 03 16:24:30 2022 -0500
tree0fdd2ebd8a2c3b1b76ee10f4bd9b0b2e9787a002
parent7a4652596ba317bf1c0366983ce90b550abebcb7 [diff]
Adjust root cause filtering for IUE thresholds

After handling an IUE threshold, a channel fail will
be initiated by firmware. If that channel fail causes
a system checkstop, we want to blame the IUE FIR bits
as the root cause.

Change-Id: Idd28b0b4310b83b97258755bc8da0dad1f58d2a6
Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
1 file changed
tree: 0fdd2ebd8a2c3b1b76ee10f4bd9b0b2e9787a002
  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. meson.build
  19. meson_options.txt
  20. OWNERS
  21. 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