Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / b116bbb0f11dfe2c39a6c63e4ae96c3cc1c6f896
commitb116bbb0f11dfe2c39a6c63e4ae96c3cc1c6f896[log] [tgz]
authorDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Thu Feb 24 06:09:37 2022 -0600
committerDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Wed Oct 12 05:40:48 2022 -0500
treed355ea629bf29deef5f371be55a7d1d27eb49b52
parent9f5573683be9dd78ad2be3cb163f46dba7d586d8 [diff]
OpenPOWER: Do not delete dump entries during mp reboot

The dump entries for the dumps stored in the host memory
should not be deleted during a memory preserved reboot.

There is a file created during memory preserved reboot
this service will not be active if the file is present

Additional change to make sure the file which indicates
memory preserving ipl is already created
https://gerrit.openbmc-project.xyz/c/openbmc/openpower-proc-control/+/51515

Tests:
During memory preserving reboot:
Feb 24 11:38:53 systemd[1]: Finished Start memory preserving reboot host0.
Feb 24 11:38:53 systemd[1]: Condition check resulted in Remove host dump entries during poweroff being skipped.

In normal poweroff
Feb 24 11:52:08 ever6bmc systemd[1]: Reached target Stop Host0 (Pre).
Feb 24 11:52:08 ever6bmc systemd[1]: Starting Remove host dump entries during poweroff...
Feb 24 11:52:08 ever6bmc systemd[1]: Starting Stop instructions for host0...
Feb 24 11:52:08 ever6bmc phosphor-dump-manager[496]: System dump delete id(3) srcdumpid(2)
Feb 24 11:52:08 ever6bmc phosphor-dump-manager[496]: System dump entry with id(3) is deleted
Feb 24 11:52:08 ever6bmc systemd[1]: Finished Remove host dump entries during poweroff.

Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Ic4269ee3322c4b8b77ea072a97e325895feed20f
1 file changed
tree: d355ea629bf29deef5f371be55a7d1d27eb49b52
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. xyz/
  7. .clang-format
  8. .gitignore
  9. bmc_dump_entry.cpp
  10. bmc_dump_entry.hpp
  11. core_manager.cpp
  12. core_manager.hpp
  13. core_manager_main.cpp
  14. dump-extensions.hpp
  15. dump_entry.cpp
  16. dump_entry.hpp
  17. dump_internal.hpp
  18. dump_manager.cpp
  19. dump_manager.hpp
  20. dump_manager_bmc.cpp
  21. dump_manager_bmc.hpp
  22. dump_manager_faultlog.cpp
  23. dump_manager_faultlog.hpp
  24. dump_manager_main.cpp
  25. dump_offload.cpp
  26. dump_offload.hpp
  27. dump_serialize.cpp
  28. dump_serialize.hpp
  29. dump_utils.cpp
  30. dump_utils.hpp
  31. elog_watch.cpp
  32. elog_watch.hpp
  33. errors_map.mako.hpp
  34. errors_map_gen.py
  35. example_errors_watch.yaml
  36. faultlog_dump_entry.cpp
  37. faultlog_dump_entry.hpp
  38. ffdc
  39. host_transport_exts.hpp
  40. LICENSE
  41. meson.build
  42. meson_options.txt
  43. OWNERS
  44. ramoops_manager.cpp
  45. ramoops_manager.hpp
  46. ramoops_manager_main.cpp
  47. README.md
  48. watch.cpp
  49. watch.hpp
README.md

phosphor-debug-collector

Phosphor Debug Collector provides mechanisms to collect various log files and system parameters. Used to troubleshoot problems in OpenBMC based systems.

To Build

To build this package with meson, do the following steps:

    1. meson builddir
    2. ninja -C builddir

To clean the built files run ninja -C builddir clean.

To run unit tests

Tests can be run in the CI docker container, refer local-ci-build

or with an OpenBMC x86 sdk(see below for x86 steps).

meson -Dtests=enabled build
ninja -C build test