Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / a08d1c373269e5d310d9ef0e4752c71e926f4a15
commita08d1c373269e5d310d9ef0e4752c71e926f4a15[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Tue Mar 01 17:51:09 2022 -0600
committerZane Shelley <zshelle@us.ibm.com>Wed Mar 02 10:01:07 2022 -0600
treeede1830cd8c40759820355a8aae029c82f4b0b44
parent9e4d1906e1db0c846a089b6c33a5036915186dba [diff]
nullptr exception when no root cause attention found

If no root cause attention found during checkstop/TI analysis, we will
continue to create the PEL with FFDC. Unfortunately in this case, the
signature for the root cause is generated from the default constructor
which sets the associated chip to nullptr. When that is used to build
the SRC words, it will throw a nullptr exception.

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