Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / a72daf5c4128b27229685c0d555ac656d6c60000
commita72daf5c4128b27229685c0d555ac656d6c60000[log] [tgz]
authorDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Wed Jun 21 13:41:42 2023 -0500
committerDhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>Wed Jun 21 14:46:35 2023 -0500
tree171d468385d847f7eb4127424287e910ca11cec3
parent0cfe1a2ee0fd9ecf69d340f7bad4a2a9c1b04d32 [diff]
OpenPOWER: Fix compile error in p10bmc

There is fix in a line missed after testing in downstream
with lastest review comment which caused the compile
failure in p10bmc

Test:
Created a system dump
busctl --verbose call xyz.openbmc_project.Dump.Manager\
  /xyz/openbmc_project/dump/system \
  xyz.openbmc_project.Dump.Create CreateDump a{sv} 0

MESSAGE "o" {
        OBJECT_PATH "/xyz/openbmc_project/dump/system/\
        entry/1";
};

Once the dump is completed check the value of
pvm_sys_dump_active
busctl call xyz.openbmc_project.BIOSConfigManager \
       /xyz/openbmc_project/bios_config/manager \
        xyz.openbmc_project.BIOSConfig.Manager \
        GetAttribute s pvm_sys_dump_active
svv "xyz.openbmc_project.BIOSConfig.Manager.AttributeType.\
     Enumeration" s "Enabled" s ""

Try another system dump
busctl --verbose call xyz.openbmc_project.Dump.Manager \
    /xyz/openbmc_project/dump/system \
    xyz.openbmc_project.Dump.Create CreateDump a{sv} 0
Call failed: The service is temporarily unavailable.

System dump is not allowed when another dump is in
progress

Change-Id: I367c4f5e58888348c33abbf813f16f2708f27ff8
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
1 file changed
tree: 171d468385d847f7eb4127424287e910ca11cec3
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. xyz/
  7. .clang-format
  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_internal.hpp
  19. dump_manager.cpp
  20. dump_manager.hpp
  21. dump_manager_bmc.cpp
  22. dump_manager_bmc.hpp
  23. dump_manager_faultlog.cpp
  24. dump_manager_faultlog.hpp
  25. dump_manager_main.cpp
  26. dump_offload.cpp
  27. dump_offload.hpp
  28. dump_serialize.cpp
  29. dump_serialize.hpp
  30. dump_utils.cpp
  31. dump_utils.hpp
  32. elog_watch.cpp
  33. elog_watch.hpp
  34. errors_map.mako.hpp
  35. errors_map_gen.py
  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. meson.build
  43. meson_options.txt
  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