Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / c3038c033f621c2b52d75a625c68040bde77fb3b
commitc3038c033f621c2b52d75a625c68040bde77fb3b[log] [tgz]
authorCaleb Palmer <cnpalmer@us.ibm.com>Mon Sep 11 10:20:56 2023 -0500
committerCaleb Palmer <cnpalmer@us.ibm.com>Tue Sep 12 10:40:47 2023 -0500
tree14f5a9a239664b58b64e920c897b791b0ba589de
parentc62813d4de33804c7ba5d82fe8ddc4a0f722c5ed [diff]
Updated analyzer root cause filtering for Odyssey special cases

This updates the RAS data analyzer's root cause filtering
to handle special cases for Odyssey OCMBs, in particular
ODP data corruption root causes, and firmware initiated
channel fails due to IUE threshold.

Signed-off-by: Caleb Palmer <cnpalmer@us.ibm.com>
Change-Id: Id22dd07b19a68007be0be3881d669eeee3a8078f
3 files changed
tree: 14f5a9a239664b58b64e920c897b791b0ba589de
  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