Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / fa5459871335906fc1cd21037ac74aca155a991d
commitfa5459871335906fc1cd21037ac74aca155a991d[log] [tgz]
authorSwarnendu-R-C <swarnendu.roy.chowdhury@ibm.com>Mon May 13 01:45:24 2024 -0500
committerSwarnendu-R-C <swarnendu.roy.chowdhury@ibm.com>Tue May 21 09:38:44 2024 -0500
tree53b4c59b120ae2a0c4ba91d1ebed0cd0431e9158
parent8f3f94da33eefc7a78f58c9a9260299ecaac3eaa [diff]
dreport: Adding redundant FW info in BMC dumps

To support additional information, the non booting FW
info is added in a separate file along with active/booting
FW in the os-release file for all the BMC dumps.

This commit includes the changes to add the redundant or
backup FW version name (if present), in a separate file
named redundant-os-release file for all the BMC dumps.

Test Results:

cat BMCDUMP.13BE960.0000053.20240510180023/redundant-os-release

REDUNDANT_FW="fw1060.00-16-1060.2420.20240508a (NL1060_042)"

Signed-off-by: Swarnendu Roy Chowdhury <swarnendu.roy.chowdhury@ibm.com>
Change-Id: Ie74df4b0371db749908b3cefc6cab6e89df442db
1 file changed
tree: 53b4c59b120ae2a0c4ba91d1ebed0cd0431e9158
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. .clang-format
  7. .gitignore
  8. .shellcheck-ignore
  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_manager.cpp
  18. dump_manager.hpp
  19. dump_manager_bmc.cpp
  20. dump_manager_bmc.hpp
  21. dump_manager_faultlog.cpp
  22. dump_manager_faultlog.hpp
  23. dump_manager_main.cpp
  24. dump_offload.cpp
  25. dump_offload.hpp
  26. dump_serialize.cpp
  27. dump_serialize.hpp
  28. dump_types.mako.cpp
  29. dump_types.mako.hpp
  30. dump_utils.cpp
  31. dump_utils.hpp
  32. elog_watch.cpp
  33. elog_watch.hpp
  34. example_dump_types.yaml
  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. map_gen.py
  42. meson.build
  43. meson.options
  44. OWNERS
  45. ramoops_manager.cpp
  46. ramoops_manager.hpp
  47. ramoops_manager_main.cpp
  48. README.md
  49. watch.cpp
  50. 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