| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_dumps.robot | 3 Documentation Test BMC dump functionality of OpenBMC.
19 # Total size of the dump in kilo bytes
22 # Minimum space required for one bmc dump in kilo bytes
25 ${BMC_DUMP_COLLECTOR_PATH} /var/lib/phosphor-debug-collector/dumps
29 Verify Error Response For Already Deleted Dump Id
30 [Documentation] Delete non existing BMC dump and expect an error.
34 ${dump_id}= Create User Initiated BMC Dump Via Redfish
35 Wait Until Keyword Succeeds 15 sec 5 sec Redfish Delete BMC Dump ${dump_id}
36 Run Keyword And Expect Error ValueError: * Redfish Delete BMC Dump ${dump_id}
39 Verify User Initiated BMC Dump When Host Powered Off
[all …]
|
| /openbmc/phosphor-debug-collector/ |
| H A D | core_manager.hpp | 12 namespace dump namespace
14 namespace core namespace
16 using Watch = phosphor::dump::inotify::Watch;
17 using UserMap = phosphor::dump::inotify::UserMap;
20 * jffs filesystem based systemd-coredump core path
33 * @brief OpenBMC Core manager implementation.
45 /** @brief Constructor to create core watch object.
46 * @param[in] event - Dump manager sd_event loop.
52 &phosphor::dump::core::Manager::watchCallback), in Manager()
57 /** @brief Helper function for initiating dump request using
[all …]
|
| H A D | core_manager.cpp | 5 #include <phosphor-logging/lg2.hpp>
13 namespace dump namespace
15 namespace core namespace
30 As per coredump source code systemd-coredump uses below format in watchCallback()
32 /var/lib/systemd/coredump/core.%s.%s." SD_ID128_FORMAT_STR “ in watchCallback()
33 systemd-coredump also creates temporary file in core file path prior in watchCallback()
34 to actual core file creation. Checking the file name format will help in watchCallback()
35 to limit dump creation only for the new core files. in watchCallback()
37 if ("core" == name.substr(0, name.find('.'))) in watchCallback()
39 // Consider only file name start with "core." in watchCallback()
[all …]
|
| H A D | meson.options | 1 # SPDX-License-Identifier: Apache-2.0
6 'jffs-workaround',
8 description: 'Turn on jffs workaround for core file',
14 value: 'xyz.openbmc_project.Dump.Manager',
15 description: 'The D-Bus busname to own',
21 value: '/xyz/openbmc_project/dump',
22 description: 'The dump manager D-Bus root',
28 value: '/xyz/openbmc_project/dump/bmc',
29 description: 'The BMC dump manager D-Bus object path',
36 description: 'Directory where core dumps are placed',
[all …]
|
| H A D | example_dump_types.yaml | 1 - xyz.openbmc_project.Dump.Create.DumpType.UserRequested:
2 - user
3 - BMC_DUMP
4 - xyz.openbmc_project.Dump.Create.DumpType.ApplicationCored:
5 - core
6 - BMC_DUMP
7 - xyz.openbmc_project.Dump.Create.DumpType.Ramoops:
8 - ramoops
9 - BMC_DUMP
10 - xyz.openbmc_project.Dump.Create.DumpType.ErrorLog:
[all …]
|
| H A D | meson.build | 1 # SPDX-License-Identifier: Apache-2.0
4 'phosphor-debug-collector',
14 license: 'Apache-2.0',
30 sdbuspp_gen_meson_prog = find_program('sdbus++-gen-meson')
33 phosphor_dbus_interfaces_dep = dependency('phosphor-dbus-interfaces')
34 phosphor_logging_dep = dependency('phosphor-logging')
36 # nlohmann-json dependency
63 add_project_arguments('-U_FORTIFY_SOURCE', language: ['cpp', 'c'])
79 description: 'The Dump manager Dbus root',
84 description: 'The BMC Dump manager Dbus path',
[all …]
|
| H A D | ramoops_manager.hpp | 11 namespace dump namespace
17 * @brief OpenBMC Core manager implementation.
30 * @param[in] filePath - Path where the ramoops are stored.
35 /** @brief Helper function for initiating dump request using
36 * createDump D-Bus interface.
37 * @param [in] files - ramoops files list
48 } // namespace dump
|
| /openbmc/phosphor-debug-collector/tools/dreport.d/ |
| H A D | README.md | 6 The phosphor-dump-manager application will automatically run dreport in certain
8 `dreport -v`.
10 ## Dump Types
12 The dump types are defined in [sample.conf](sample.conf):
14 - core: Triggered by an application core dump
15 - user: The type when manually called, such as from running `dreport`.
16 - elog: Triggered when there are specific phosphor-logging event logs.
17 - checkstop: Triggered on a specific type of host crash.
18 - ramoops: Triggered when there is a kernel panic.
23 They can call [provided functions](include.d/functions) to add data to the dump
[all …]
|
| H A D | dreport | 14 -n, —-name <name> Name to be used for the archive.
16 -d, —-dir <directory> Archive directory to copy the compressed report.
18 -i, —-id <id> Dump identifier to associate with the archive.
20 Default dump identifier is 0
21 -t, —-type <type> Data collection type. Valid types are
22 "user", "core", "elog".
24 -p, —-path <path> Optional contents to be included in the archive.
25 Valid paths are absolute file path or d-bus path
27 -Absolute file path for "core" type.
28 -elog d-bus object for "elog" type.
[all …]
|
| /openbmc/docs/designs/ |
| H A D | ncsi-coredump.md | 1 # NC-SI core dump
9 NIC core-dump is essential for NIC issue debugging, and it could be retrieved
10 via both in-band and out of band method. The design here is providing the
11 solution for NIC out of band dumping from BMC over NC-SI protocol.
15 NC-SI command for dump retrieval: Reference: NC-SI spec v1.2: section: 8.4.114
18 NC-SI over MCTP:
23 This feature requires Linux kernel to support transferring new NC-SI command
31 This design will reuse existing phosphor-debug-collector module:
32 <https://github.com/openbmc/phosphor-debug-collector> and extend the dump
33 creation interface with a new "NC-SICoreDump" dump type.
[all …]
|
| H A D | dump-manager.md | 1 # Dump Manager Design
14 required for the debugging needs to be collected as a dump. The existing OpenBMC
15 dump interfaces support only the dumps generated on the BMC and dump manager
20 - **System Dump**: A dump of the Host's main memory and processor registers.
22 - **Memory Preserving Reboot(MPR)**: A method of reboot with preserving the
24 - **PLDM**: An interface and data model to access low-level platform inventory,
26 [ReadMore](https://github.com/openbmc/docs/blob/master/designs/pldm-stack.md)
27 - **Machine Check Exception**: A severe error inside a processor core that
28 causes a processor core to stop all processing activities.
29 - **BMCWeb**: An embedded webserver for OpenBMC.
[all …]
|
| H A D | power-systems-memory-preserving-reboot.md | 1 # Memory preserving reboot and System Dump extraction flow on POWER Systems
15 don't have access to a non-volatile storage to store this content after a
17 based servers to create a memory dump required for the debugging. This document
18 explains the high-level flow of warm reboot and extraction of the resulting dump
23 - **Boot**: The process of initializing hardware components in a computer system
26 - **Hostboot**: The firmware runs on the host processors and performs all
28 [read more](https://github.com/open-power/docs/blob/master/hostboot/HostBoot_PG.md)
30 - **Self Boot Engine (SBE)**: A microcontroller built into the host processors
35 - **Master Processor**: The processor which gets initialized first to execute
38 - **POWER Hardware Abstraction Layer (PHAL)**: A software component on the BMC
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | Create.interface.yaml | 3 interface is for user to request a particular type of dump.
6 xyz.openbmc_project.Dump.Create per dump type on
7 /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9 /xyz/openbmc_project/dump/<dump type><instance-id>.
12 - name: CreateDump
14 Method to create a manual Dump.
16 - name: AdditionalData
19 The additional data, if any, for initiating the dump. The key in
21 the specific type of dump either in xyz or in a domain. The
23 enum-format string is required to come from a parallel class
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-bsp/grub/files/ |
| H A D | CVE-2025-1118.patch | 4 Subject: [PATCH] commands/minicmd: Block the dump command in lockdown mode
6 The dump enables a user to read memory which should not be possible
9 Fixes: CVE-2025-1118
11 Reported-by: B Horn <b@horn.uk>
12 Reported-by: Jonathan Bar Or <jonathanbaror@gmail.com>
13 Signed-off-by: B Horn <b@horn.uk>
14 Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
16 CVE: CVE-2025-1118
17 Upstream-Status: Backport [https://git.savannah.gnu.org/cgit/grub.git/commit/?id=34824806ac6302f91e…
18 Signed-off-by: Peter Marko <peter.marko@siemens.com>
[all …]
|
| /openbmc/openpower-debug-collector/dump/tools/bmcdump/plugins/ |
| H A D | dumpfilelist | 4 # @brief: Get the dump and core file information
10 #core files
13 command="busctl call --verbose --no-pager \
14 xyz.openbmc_project.Dump.Manager \
15 /xyz/openbmc_project/dump \
21 dir="/var/lib/phosphor-debug-collector/dumps/"
23 if [ -d "$dir" ] && [ -n "$(ls -A $dir/)" ]; then
25 add_cmd_output "ls -AX $dir/*/*" "$file_name" "$desc"
31 dir="/var/lib/phosphor-debug-collector/hardwaredump/"
33 if [ -d "$dir" ] && [ -n "$(ls -A $dir/)" ]; then
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/recipes-httpd/apache2/apache2/ |
| H A D | 0002-apache2-bump-up-the-core-size-limit-if-CoreDumpDirec.patch | 4 Subject: [PATCH] apache2: bump up the core size limit if CoreDumpDirectory is
7 Bump up the core size limit if CoreDumpDirectory is
10 Upstream-Status: Pending
14 ---
15 server/core.c | 19 +++++++++++++++++++
18 diff --git a/server/core.c b/server/core.c
20 --- a/server/core.c
21 +++ b/server/core.c
22 @@ -5143,6 +5143,25 @@ static int core_post_config(apr_pool_t *pconf, apr_pool_t *plog, apr_pool_t …
35 + "core dump file size limit raised to %lu bytes",
[all …]
|
| /openbmc/linux/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| D | debug.c | |
| /openbmc/linux/Documentation/arch/s390/ |
| D | zfcpdump.rst | |
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/ |
| D | iwl-context-info.h | |
| /openbmc/openbmc/meta-phosphor/recipes-core/systemd/phosphor-systemd-policy/ |
| H A D | service-restart-policy.conf | 3 # - Change the RestartSec from 100ms to 1s.
5 # in. When a core file is involved, it's been found that generating 5 core
10 # - Change the StartLimitBurst to 2
12 # scenarios seen so far (other then with phosphor-hwmon), either
16 # - Change the StartLimitIntervalSec to 30s
18 # failing and a core dump is being generated and collected into a dump,
20 # the service does not fail again until 15-20 seconds after the initial
26 # See systemd-system.conf(5) for details on the conf files
|
| /openbmc/openbmc-test-automation/redfish/ |
| H A D | test_xit.robot | 13 ${ERROR_REGEX} SEGV|core-dump|FAILURE|Failed to start|Found ordering cycle
19 Verify No BMC Dump And Application Failures In BMC
20 [Documentation] Verify no BMC dump and application failure exists in BMC.
23 # Check dump entry based on Redfish API availability.
25 ${resp}= Redfish.Get /redfish/v1/Managers/${MANAGER_ID}/LogServices/Dump/Entries
35 …Check For Regex In Journald ${ERROR_REGEX} error_check=${0} boot=-b filter_string=${SKIP_ERROR}
44 # Remove rm command once the BMC dump APIs are working.
45 … Run Keyword And Ignore Error BMC Execute Command rm -rf /var/lib/phosphor-debug-collector/dumps/
|
| /openbmc/linux/drivers/firmware/broadcom/ |
| D | tee_bnxt_fw.c | |
| /openbmc/phosphor-debug-collector/service_files/ |
| H A D | obmc-dump-monitor.service | 2 Description=Phosphor Dump core monitor.
6 ExecStart=/usr/libexec/phosphor-debug-collector/phosphor-dump-monitor
10 WantedBy=multi-user.target
|
| /openbmc/qemu/qapi/ |
| H A D | dump.json | 1 # -*- Mode: Python -*-
5 # See the COPYING file in the top-level directory.
9 # Dump guest memory
16 # An enumeration of guest-memory-dump's format.
20 # @kdump-zlib: makedumpfile flattened, kdump-compressed format with
23 # @kdump-lzo: makedumpfile flattened, kdump-compressed format with lzo
26 # @kdump-snappy: makedumpfile flattened, kdump-compressed format with
29 # @kdump-raw-zlib: raw assembled kdump-compressed format with zlib
32 # @kdump-raw-lzo: raw assembled kdump-compressed format with lzo
35 # @kdump-raw-snappy: raw assembled kdump-compressed format with snappy
[all …]
|
| /openbmc/linux/drivers/net/wireless/ath/wil6210/ |
| D | wil_crash_dump.c | |