Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 513f64aa8610064e3e5655d1bcd5cb4babe34bd9
commit513f64aa8610064e3e5655d1bcd5cb4babe34bd9[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Wed Jun 15 09:02:29 2022 -0500
committerZane Shelley <zshelle@us.ibm.com>Wed Jun 15 09:55:39 2022 -0500
tree414276ced25df7c6719897aa0402b840dbe7d068
parent4efca2808c4221a17e7b7483df1ec7751b2873e7 [diff]
Handling for host detected LPC timeout

For reasons not explained yet, hardware will not initiate an LPC timeout
attention via NCU timeout FIR bit as we expected. When the host firmware
detects an LPC timeout, it will manually set N1_LOCAL_FIR[61] to force a
system checkstop. The service response for this bit will be to call out
the hardware as if there was a hardware reported LPC timeout.

Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
Change-Id: I863e8aa3ef50a4b18b5106b3a45c4cf81b2c7808
3 files changed
tree: 414276ced25df7c6719897aa0402b840dbe7d068
  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