Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 0c782d64f6640fd0adf532380259003c314bb5d8
commit0c782d64f6640fd0adf532380259003c314bb5d8[log] [tgz]
authorDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Wed Mar 24 13:27:13 2021 -0500
committerDhruvaraj S <dhruvaraj@gmail.com>Thu Mar 25 13:59:37 2021 +0000
tree531753322e0142e432a45fe932c219a5a04fd3ac
parent01c664606479dfaf9fc3745412e20be4d09447f2 [diff]
Error while invalidating the resource dump over PLDM.

Problem:
The wrong identifier type was passed to the host dump
transport for deleting the dump, so an exception
is thrown.
Fix was needed in two places
1) Dump identifier number was old in resource dump manager
2) PLDM_FILE_TYPE_RESOURCE_DUMP_PARAMS was given as dump
identifier instead of PLDM_FILE_TYPE_RESOURCE_DUMP.
Test:
- Created a new dump
- Invalidated the dump
Result: Dump is deleted from the host.

Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: If68f415439d8322f47fa6a6bc7a9b230e9f67fb1
2 files changed
tree: 531753322e0142e432a45fe932c219a5a04fd3ac
  1. dump-extensions/
  2. host-transport-extensions/
  3. test/
  4. tools/
  5. xyz/
  6. .clang-format
  7. .gitignore
  8. bmc_dump_entry.cpp
  9. bmc_dump_entry.hpp
  10. core_manager.cpp
  11. core_manager.hpp
  12. core_manager_main.cpp
  13. dump-extensions.hpp
  14. dump_entry.cpp
  15. dump_entry.hpp
  16. dump_internal.hpp
  17. dump_manager.cpp
  18. dump_manager.hpp
  19. dump_manager_bmc.cpp
  20. dump_manager_bmc.hpp
  21. dump_manager_main.cpp
  22. dump_offload.cpp
  23. dump_offload.hpp
  24. dump_serialize.cpp
  25. dump_serialize.hpp
  26. dump_utils.cpp
  27. dump_utils.hpp
  28. elog_watch.cpp
  29. elog_watch.hpp
  30. errors_map.mako.hpp
  31. errors_map_gen.py
  32. example_errors_watch.yaml
  33. ffdc
  34. host_transport_exts.hpp
  35. LICENSE
  36. MAINTAINERS
  37. meson.build
  38. meson_options.txt
  39. README.md
  40. watch.cpp
  41. 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 -Doe-sdk=enabled -Dtests=enabled build
ninja -C build test