Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / b89a476e3c5de5843920a40d36c7df3c129865a6
commitb89a476e3c5de5843920a40d36c7df3c129865a6[log] [tgz]
authorDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Thu Jun 29 05:35:07 2023 -0500
committerDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Sun Jul 16 07:14:55 2023 -0500
treec00f6adbd4a6373525f2d0a00f8c847df2edea6e
parent8bea993c3df316690e57ece4ccd07bdd3707574b [diff]
Add Ramoops dump to common create

This commit adjusts the handling of ramoops (RAM OOPS)
dumps to use the common BMC dump creation interface.
Previously, when a ramoops dump was detected, the
ramoops manager would inform the dump manager via an
internal D-Bus interface. With the changes in this
commit, upon detecting a ramoops event, the ramoops
manager will now request the dump manager to create
a BMC dump, incorporating the relevant ramoops data,
via the common create DBus interface.

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

One such mechanism is dreport, a script that collects debug data and packages it into an archive file.

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