Add entity-objects D-Bus objects to dump

There are some associations that are useful for debug and just getting
them from entity-manager as opposed to the mapper is less resource
intensive and takes

Add entity-objects D-Bus objects to dump

There are some associations that are useful for debug and just getting
them from entity-manager as opposed to the mapper is less resource
intensive and takes up a smaller amount of space in the dump.

Tested:
The file and the data are in the dump:
```
~/BMCDUMP.XXXXXXX.00000000.20250226205426_out/archive$ head emobjects.log
MESSAGE "a{oa{sa{sv}}}" {
ARRAY "{oa{sa{sv}}}" {
DICT_ENTRY "oa{sa{sv}}" {
OBJECT_PATH "/xyz/openbmc_project/inventory/system/board/Ingraham_Board";
ARRAY "{sa{sv}}" {
DICT_ENTRY "sa{sv}" {
STRING "org.freedesktop.DBus.Peer";
ARRAY "{sv}" {
};
};

```

Change-Id: I612b59b1a0d9483b33beae05f04ab82eafbe72cf
Signed-off-by: Matt Spinler <spinler@us.ibm.com>

show more ...

meson: reformat with meson formatter

Apply the `meson format` results.

Change-Id: I1038d734aa030fc63345280a846c34c5b70b0d16
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

Faultlog: Add support to install Faultlog

Add faultlog to bmcdump plugins and include faultlog in dreport_op.conf
which shall install the plugin from meta-ibm layer in openbmc repo
and creates sym-l

Faultlog: Add support to install Faultlog

Add faultlog to bmcdump plugins and include faultlog in dreport_op.conf
which shall install the plugin from meta-ibm layer in openbmc repo
and creates sym-link.

Test Results:
Verified that openpower-debug-collector recipe installs faultlog script

sysroot-destdir$ ls usr/share/dreport.d/pl_faultdata.d
E10faultlog

Change-Id: I46ece91a04d4d40a3bd72771d6fea11468e5e403
Signed-off-by: Gopichand Paturi <gopichandpaturi@gmail.com>

show more ...

opfunctions: Fix dumpId length

Dump Id in BMC Dump Filename is padded to 7 digits instead of 8 digits.
This is causing file name mismatch between the dump offloaded to
HMC/OS and the dump stored on

opfunctions: Fix dumpId length

Dump Id in BMC Dump Filename is padded to 7 digits instead of 8 digits.
This is causing file name mismatch between the dump offloaded to
HMC/OS and the dump stored on BMC. Fixing this issue by padding Dump
Id to 8 digits.

Test Results:

Before:
root@p10bmc:/var/lib/phosphor-debug-collector/dumps/6# ls
BMCDUMP.13ECF8X.0000006.20241001051003

After:
root@p10bmc:/var/lib/phosphor-debug-collector/dumps/17# ls
BMCDUMP.1012345.00000017.20330125023119

Change-Id: I04c469ad3aaf6480c5732445ba7f8e644357262e
Signed-off-by: SwethaParasa <parasa.swetha1@ibm.com>

show more ...

opdreport: Eliminate undeclared variable; use existing variable instead

The variable 'id' is not declared anywhere in the code, but it is
used for determining the dump content type in the code. Beca

opdreport: Eliminate undeclared variable; use existing variable instead

The variable 'id' is not declared anywhere in the code, but it is
used for determining the dump content type in the code. Because of
this, dump content type is not populated correctly which is causing
a failure in determining dump type when the dump is parsed using
'makedump' tool. So, removing usage of variable 'id' and using
'dump_id' instead of it to solve this issue.

Test Results:

Before:
>>>> Processing dump files
  Processing: SYSDUMP.13E09F0.00000007.20240913135832
  Dump Type is: UNKNOWN

>>>> Processing dump files
  Processing: SYSDUMP.13ECF8X.20000008.20240916083507
Dump Type is: UNKNOWN

After:
>>>> Processing dump files
Processing: SYSDUMP.1012345.00000008.20240903113715
Dump Type is: SCS

>>>> Processing dump files
Processing: SYSDUMP.1012345.20000007.20240903113517
Dump Type is: HB

>>>> Processing dump files
Processing: SYSDUMP.1012345.20000010.20240903140425
Dump Type is: HB

>>>> Processing dump files
Processing: SYSDUMP.1012345.00000011.20240903140502
Dump Type is: SCS

Change-Id: If41f2d652a2b75cce78f50cb64bbf5ff56b87e98
Signed-off-by: SwethaParasa <parasa.swetha1@ibm.com>

show more ...

Fix spelling mistakes using codespell

This commit corrects various spelling mistakes throughout the
repository. The corrections were made automatically using `codespell`[1]
tool.

[1]: https://githu

Fix spelling mistakes using codespell

This commit corrects various spelling mistakes throughout the
repository. The corrections were made automatically using `codespell`[1]
tool.

[1]: https://github.com/codespell-project/codespell

Change-Id: Ib615c5fe1dfb01fc0adedd692524fe145c8c4e82
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>

show more ...

Move dump scripts from phosphor-debug-collector

This commit is intended to move the dump collection
scripts from openbmc/phosphor-debug-collector repository.
Following are the scripts that are pulle

Move dump scripts from phosphor-debug-collector

This commit is intended to move the dump collection
scripts from openbmc/phosphor-debug-collector repository.
Following are the scripts that are pulled from the
specified paths of openbmc/phosphor-debug-collector.

1. tools/dreport.d/ibm.d/package
2. tools/dreport.d/ibm.d/plugins.d/pels
3. tools/dreport.d/ibm.d/plugins.d/badpel
4. tools/dreport.d/ibm.d/plugins.d/vpd_data
5. tools/dreport.d/openpower.d/plugins.d/cfam
6. tools/dreport.d/openpower.d/plugins.d/dumpfilelist
7. tools/dreport.d/openpower.d/plugins.d/guardlist
8. tools/dreport.d/openpower.d/plugins.d/obmcconsole1
9. tools/dreport.d/openpower.d/plugins.d/occ
10.tools/dreport.d/openpower.d/plugins.d/phal_devtree

Also the following 3 patches have been applied.
1.https://gerrit.openbmc.org/c/openbmc/phosphor-debug-collector/+/56428
2.https://gerrit.openbmc.org/c/openbmc/phosphor-debug-collector/+/52436
3.https://gerrit.openbmc.org/c/openbmc/phosphor-debug-collector/+/47917

Also, added meson changes to install the scripts.

Test:
Verified that the scripts are getting installed correctly on BMC.

Change-Id: Iaddf909efaa138db06c877e5ca6a80608feb5baf
Signed-off-by: Gopichand Paturi <gopichandpaturi@gmail.com>

show more ...

Add script to generate dump info file

This commit introduces the gendumpinfo script which generates the
info.yaml file containing metadata about the dump. It also updates
the meson.build files to in

Add script to generate dump info file

This commit introduces the gendumpinfo script which generates the
info.yaml file containing metadata about the dump. It also updates
the meson.build files to include this script in the build process
and ensures it gets installed correctly.

Change-Id: Idcd550ceac912ff42ce2df2bfcb333b4c8b8644b
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

show more ...

Add opdreport tool to OpenPOWER Debug Collector

This commit introduces the opdreport tool, which creates an archive
consisting of host dump files and applies headers on top of it. The
tool includes

Add opdreport tool to OpenPOWER Debug Collector

This commit introduces the opdreport tool, which creates an archive
consisting of host dump files and applies headers on top of it. The
tool includes options to specify the name, directory, dump ID,
maximum allowed size, failing unit, error log ID, and type of the dump
to be collected.

Changes:
- Added meson.build files to integrate opdreport tool.
- Updated meson.build to conditionally include the dump subdirectory
based on the dump-collection option.
- Added opdreport script to the tools/opdump directory.
- Modified meson.build to handle installation of opdreport.

Change-Id: I1a83b2bf4ffa6f8f47191df17b35f8d5b13e4115
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

show more ...

Create Dump Header for IBM Systems

Creating a dump header for IBM systems involves adding a new script to
generate these headers specifically for IBM. This change only impacts
IBM-specific systems a

Create Dump Header for IBM Systems

Creating a dump header for IBM systems involves adding a new script to
generate these headers specifically for IBM. This change only impacts
IBM-specific systems and does not alter the existing dump package format
for other systems. For IBM systems, the generated header will be
appended to the dump, ensuring compatibility with the existing dump
process. Non-IBM systems will continue to use the current dump format
without any modifications. This enhancement maintains the integrity and
format of dumps across different systems while providing a consistent
and specific dump format for IBM systems.

Change-Id: Id6540c90d7519cdd3a96af691a32d906c5e5b63e
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

show more ...