History log of /openbmc/openpower-debug-collector/dump/ (Results 26 – 30 of 30)
Revision Date Author Comments
(<<< Hide modified files)
(Show modified files >>>)
5f5c94d519-Oct-2021 Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

Collect SBE dump during chip-op timeouts

Add support for collecting SBE dump during dump chip-op
failure.
- Request SBE dump in the case of a chip-op timeout
- Wait for the dump to complete the ti

Collect SBE dump during chip-op timeouts

Add support for collecting SBE dump during dump chip-op
failure.
- Request SBE dump in the case of a chip-op timeout
- Wait for the dump to complete the timeout

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

show more ...

62881c5320-Sep-2021 Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

Add support for collecting Self Boot Engine(SBE) dump

SBE is a microcontroller that sits inside the processor
to initialize it to start the booting procedure. It also acts as
a secure channel for ac

Add support for collecting Self Boot Engine(SBE) dump

SBE is a microcontroller that sits inside the processor
to initialize it to start the booting procedure. It also acts as
a secure channel for accessing certain control functions on
the processor. During the booting or other hardware access operations
SBE can encounter errors and become unresponsive. In such situations,
the debug data needs to be collected from such SBEs to find out
the root cause of the error.
This data may include hardware state, configuration, memory, etc.
The collected data is then packaged into the OpenPOWER dump format
and which is to be called as SBE dump.

The SBE dump is collected from an responsive SBE using special
procedures which is executing hardware access instructions
to get the memory and other hardware states. This commit adds
support for calling such procedure implementations.

Test:
Execute SBE dump collection during dump-collect

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

show more ...

6feeebd619-Oct-2021 Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

Add PEL creation for SBE chip-op failures

This commit introduces a new function within the SBE dump collection
mechanism to create PELs) when chip operations on SBE fail.

Test:
Make sure the PELs a

Add PEL creation for SBE chip-op failures

This commit introduces a new function within the SBE dump collection
mechanism to create PELs) when chip operations on SBE fail.

Test:
Make sure the PELs are logged during chip-op failure

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

show more ...

a699e31e27-Oct-2021 Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

Update SBE dump collection process and error handling

This commit added the dump collection from SBE. It introduces the
capability to invoke the getdump chip operation on the SBE) and
added traces f

Update SBE dump collection process and error handling

This commit added the dump collection from SBE. It introduces the
capability to invoke the getdump chip operation on the SBE) and
added traces for any failures encountered during the operation.

In addition to the above, this update brings in a new utility function
designed to write the collected dump data into a specified file format
and path.

Furthermore, the commit incorporates a logic check function to determine
the necessity of fastarray data collection when performing the dump from
SBE. This addition optimizes the dump collection process by selectively
gathering fastarray data only when it's deemed necessary.

The dump-collect application reports a failure if the destination path
remains empty post-operation, indicating that no dump files were
successfully collected from any of the SBEs.

Tests:
- Collect hardware dump
- Collect hostboot dump

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

show more ...

858d1aaf27-Oct-2021 Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

dump-collect: Add application for SBE dump collection

This series of commits introduces the `dump-collect` application, a new
command-line tool designed to facilitate the collection of dumps from
th

dump-collect: Add application for SBE dump collection

This series of commits introduces the `dump-collect` application, a new
command-line tool designed to facilitate the collection of dumps from
the SBE. The tool is capable of asynchronous operation, allowing it
to initiate dump collection from different SBEs at the same time.

Key Highlights:
- The base implementation sets up the application to accept necessary
parameters for dump collection, including dump type, dump ID,
destination path for collected data, and the ID of the failing unit.
- An implementation of the dump collection class and the initiation
method enables the start of the dump collection process
asynchronously.
- The `dump-collect` application is designed to be invoked from scripts,
which collect various data in the case of system failures.

Tests:
Validated parameters passed
Starting dump collection method

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

show more ...


/openbmc/openpower-debug-collector/.clang-format
/openbmc/openpower-debug-collector/.gitignore
/openbmc/openpower-debug-collector/LICENSE
/openbmc/openpower-debug-collector/OWNERS
/openbmc/openpower-debug-collector/README.md
/openbmc/openpower-debug-collector/checkstop_app.cpp
dump_collect_main.cpp
dump_utils.cpp
dump_utils.hpp
meson.build
sbe_consts.hpp
sbe_dump_collector.cpp
sbe_dump_collector.hpp
/openbmc/openpower-debug-collector/meson.build
/openbmc/openpower-debug-collector/meson.options
/openbmc/openpower-debug-collector/subprojects/CLI11.wrap
/openbmc/openpower-debug-collector/subprojects/phosphor-logging.wrap
/openbmc/openpower-debug-collector/subprojects/sdbusplus.wrap
/openbmc/openpower-debug-collector/watchdog/ffdc_file.cpp
/openbmc/openpower-debug-collector/watchdog/ffdc_file.hpp
/openbmc/openpower-debug-collector/watchdog/file_descriptor.hpp
/openbmc/openpower-debug-collector/watchdog/meson.build
/openbmc/openpower-debug-collector/watchdog/utils.cpp
/openbmc/openpower-debug-collector/watchdog/utils.hpp
/openbmc/openpower-debug-collector/watchdog/watchdog_common.cpp
/openbmc/openpower-debug-collector/watchdog/watchdog_common.hpp
/openbmc/openpower-debug-collector/watchdog/watchdog_dbus.cpp
/openbmc/openpower-debug-collector/watchdog/watchdog_dbus.hpp
/openbmc/openpower-debug-collector/watchdog/watchdog_handler.cpp
/openbmc/openpower-debug-collector/watchdog/watchdog_handler.hpp
/openbmc/openpower-debug-collector/watchdog/watchdog_logging.cpp
/openbmc/openpower-debug-collector/watchdog/watchdog_logging.hpp
/openbmc/openpower-debug-collector/watchdog/watchdog_main.cpp
/openbmc/openpower-debug-collector/watchdog/watchdog_main.hpp
/openbmc/openpower-debug-collector/watchdog_timeout.cpp

12