Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 0df38f719532182506c0b0d32ba7e6e9a20193b9
commit0df38f719532182506c0b0d32ba7e6e9a20193b9[log] [tgz]
authorSwarnendu-R-C <Swarnendu.Roy.Chowdhury@ibm.com>Fri Jul 19 06:38:32 2024 -0500
committerGopichand Paturi <gopichandpaturi@gmail.com>Wed Apr 16 20:38:37 2025 -0500
tree00b1d5b0c16294d7a93c720657b3c4a4f5d8c766
parentbd00955bd5a000b245fa0420153875bbd9b6022f [diff]
dreport: Min FW info added

It has been requested that while generating BMC dumps
it should include minimum F/W level supported info.

These changes aim to incorporate the above said request
by creating one plugin, namely minfwlevelinfo, under
dreport. If in case the info is not available then it
logs a related warning in dreportlog file about it.

Also the redundantosrelease plugin file has been modified
because both the plugins, redundantosrelease and minfwlevelinfo
use same lines of code almost, and thus, putting that in the
functions script we can make them available for both the
plugins. And with little bit of pre checks in the related
plugins we avoid unnecessary repetitive calls of the same
code and dbus invokes.

Test Results:

Tested for both the plugins for both positive and negative
cases and found the results as per the expectations

Signed-off-by: Swarnendu Roy Chowdhury <swarnendu.roy.chowdhury@ibm.com>
Signed-off-by: Gopichand Paturi <gopichandpaturi@gmail.com>
Change-Id: Ib530ea5e86923dea10302f2931cd53c0dfbce21e
3 files changed
tree: 00b1d5b0c16294d7a93c720657b3c4a4f5d8c766
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. .clang-format
  7. .clang-tidy
  8. .gitignore
  9. .shellcheck-ignore
  10. bmc_dump_entry.cpp
  11. bmc_dump_entry.hpp
  12. core_manager.cpp
  13. core_manager.hpp
  14. core_manager_main.cpp
  15. dump-extensions.hpp
  16. dump_entry.cpp
  17. dump_entry.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_types.cpp.mako
  30. dump_types.hpp.mako
  31. dump_utils.cpp
  32. dump_utils.hpp
  33. elog_watch.cpp
  34. elog_watch.hpp
  35. example_dump_types.yaml
  36. example_errors_watch.yaml
  37. faultlog_dump_entry.cpp
  38. faultlog_dump_entry.hpp
  39. ffdc
  40. host_transport_exts.hpp
  41. LICENSE
  42. map_gen.py
  43. meson.build
  44. meson.options
  45. OWNERS
  46. ramoops_manager.cpp
  47. ramoops_manager.hpp
  48. ramoops_manager_main.cpp
  49. README.md
  50. watch.cpp
  51. 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