| /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 | 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 | 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 …]
|
| /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/linux/sound/soc/intel/avs/ |
| H A D | skl.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 // Copyright(c) 2021-2022 Intel Corporation. All rights reserved.
20 u32 size, num_cores = adev->hw_cfg.dsp_cores; in avs_skl_enable_logs()
24 return -EINVAL; in avs_skl_enable_logs()
28 return -ENOMEM; in avs_skl_enable_logs()
30 info->core_mask = resource_mask; in avs_skl_enable_logs()
33 info->logs_core[i].enable = enable; in avs_skl_enable_logs()
34 info->logs_core[i].min_priority = *priorities++; in avs_skl_enable_logs()
38 info->logs_core[i].enable = enable; in avs_skl_enable_logs()
48 int avs_skl_log_buffer_offset(struct avs_dev *adev, u32 core) in avs_skl_log_buffer_offset() argument
[all …]
|
| H A D | apl.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 // Copyright(c) 2021-2022 Intel Corporation. All rights reserved.
21 u32 size, num_cores = adev->hw_cfg.dsp_cores; in avs_apl_enable_logs()
25 return -EINVAL; in avs_apl_enable_logs()
29 return -ENOMEM; in avs_apl_enable_logs()
31 info->aging_timer_period = aging_period; in avs_apl_enable_logs()
32 info->fifo_full_timer_period = fifo_full_period; in avs_apl_enable_logs()
33 info->core_mask = resource_mask; in avs_apl_enable_logs()
36 info->logs_core[i].enable = enable; in avs_apl_enable_logs()
37 info->logs_core[i].min_priority = *priorities++; in avs_apl_enable_logs()
[all …]
|
| /openbmc/linux/fs/ |
| H A D | Kconfig.binfmt | 1 # SPDX-License-Identifier: GPL-2.0-only
18 however) and makes building run-time libraries very easy. Many new
78 bool "Write ELF core dumps with partial segments"
82 ELF core dump files describe each memory mapping of the crashed
87 the first page of the file in a core dump makes it possible to
89 cost and disk space to dump all the text. However, versions of
90 GDB before 6.7 are confused by ELF core dump files in this format.
92 The core dump behavior can be controlled per process using
93 the /proc/PID/coredump_filter pseudo-file; this setting is
148 If you say Y here, it will be possible to plug wrapper-driven binary
[all …]
|
| H A D | coredump.c | 1 // SPDX-License-Identifier: GPL-2.0
61 static char core_pattern[CORENAME_MAX_SIZE] = "core";
74 corename = krealloc(cn->corename, size, GFP_KERNEL); in expand_corename()
77 return -ENOMEM; in expand_corename()
82 cn->size = size; in expand_corename()
83 cn->corename = corename; in expand_corename()
94 free = cn->size - cn->used; in cn_vprintf()
97 need = vsnprintf(cn->corename + cn->used, free, fmt, arg_copy); in cn_vprintf()
101 cn->used += need; in cn_vprintf()
105 if (!expand_corename(cn, cn->size + need - free + 1)) in cn_vprintf()
[all …]
|
| /openbmc/linux/Documentation/admin-guide/kdump/ |
| H A D | kdump.rst | 2 Documentation for Kdump - The kexec-based Crash Dumping Solution
11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
14 the reboot and is accessible to the dump-capture kernel.
17 the memory image to a dump file on the local disk, or across the network
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
44 All of the necessary information about the system kernel's core image is
47 passed to the dump-capture kernel through the elfcorehdr= boot
[all …]
|
| /openbmc/phosphor-debug-collector/tools/dreport.d/openpower.d/plugins.d/ |
| 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/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/linux/Documentation/powerpc/ |
| H A D | firmware-assisted-dump.rst | 2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
13 the existing phyp assisted dump.
14 - Fadump uses the same firmware interfaces and memory reservation model
15 as phyp assisted dump.
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
18 kdump infrastructure for dump capture and filtering.
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
[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/Documentation/arch/s390/ |
| H A D | zfcpdump.rst | 2 The s390 SCSI dump tool (zfcpdump)
6 dumps on SCSI disks. The dump process is initiated by booting a dump tool, which
7 has to create a dump of the current (probably crashed) Linux image. In order to
8 not overwrite memory of the crashed Linux with data of the dump tool, the
10 dump tool is loaded. There exists an SCLP hardware interface to obtain the saved
13 This zfcpdump implementation consists of a Linux dump kernel together with
14 a user space dump tool, which are loaded together into the saved memory region
16 the s390-tools package) to make the device bootable. The operator of a Linux
17 system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump
20 The user space dump tool accesses the memory of the crashed system by means
[all …]
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/ |
| H A D | iwl-context-info.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */
4 * Copyright (C) 2018-2020, 2022 Intel Corporation
14 * enum iwl_context_info_flags - Context information control flags
18 * @IWL_CTXT_INFO_ENABLE_CDMP: enable core dump
20 * exponent, the actual size is 2**value, valid sizes are 8-2048.
23 * default is short format - not supported by the driver)
57 * struct iwl_context_info_version - version structure
70 * struct iwl_context_info_control - version structure
79 * struct iwl_context_info_dram - images DRAM map
92 * struct iwl_context_info_rbd_cfg - RBDs configuration
[all …]
|
| /openbmc/linux/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| H A D | debug.c | 1 // SPDX-License-Identifier: ISC
12 #include "core.h"
20 void *dump; in brcmf_debug_create_memdump() local
26 return -ENOTSUPP; in brcmf_debug_create_memdump()
28 dump = vzalloc(len + ramsize); in brcmf_debug_create_memdump()
29 if (!dump) in brcmf_debug_create_memdump()
30 return -ENOMEM; in brcmf_debug_create_memdump()
33 memcpy(dump, data, len); in brcmf_debug_create_memdump()
34 err = brcmf_bus_get_memdump(bus, dump + len, ramsize); in brcmf_debug_create_memdump()
36 vfree(dump); in brcmf_debug_create_memdump()
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
3 Contact: linux-crypto@vger.kernel.org
4 Description: Dump debug registers from the HPRE cluster.
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
9 Contact: linux-crypto@vger.kernel.org
10 Description: Write the HPRE core selection in the cluster into this file,
11 and then we can read the debug information of the core.
16 Contact: linux-crypto@vger.kernel.org
25 Contact: linux-crypto@vger.kernel.org
32 Contact: linux-crypto@vger.kernel.org
[all …]
|