| /openbmc/docs/designs/ |
| 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.
35 dump manager, which is orchestrating the collection and offload, needs to
36 provide methods to create, store the dump details, and offload it. Additionally,
37 some sources allow the dump to be extracted manually without a failure to
42 These are some of the dumps supported by dump manager.
44 #### BMC Dump
46 A dump collected when there is a failure in the BMC with various debug
[all …]
|
| H A D | power-systems-memory-preserving-reboot.md | 1 # Memory preserving reboot and System Dump extraction flow on POWER Systems.
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
45 - **System Dump**: A dump of main memory and hardware states for debugging the
82 collects the hardware data and memory contents to create a dump file in the host
89 - System dump should be collected irrespective of the availability of an
92 - It should provide a mechanism for the user to request a system dump.
106 - Error log associated with dump needs to be part of the dump package
108 - A dump summary should be created with size and other details of the dump
110 - Once the dump is generated, the hypervisor should notify BMC.
[all …]
|
| /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
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
40 [Documentation] Create user initiated BMC dump at host off state and
[all …]
|
| /openbmc/phosphor-debug-collector/tools/dreport.d/ibm.d/ |
| H A D | gendumpheader | 3 #Header for BMC DUMP
5 #This script will generate generic IBM dump header format.
7 #Note: The dump header will be imposed on the dump file i.e
9 #separate out the header before extracting the dump.
58 #Function to fetch the size of the dump
60 #Adding 516 bytes as the total dump size is dump tar size
61 #plus the dump header entry in this case
79 #Function to set dump id to 8 bytes format
103 #Dump File Type 7 BMCDUMP
106 #Dump Identifier 8 Dump Identifier value fetched from dump
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | dump_utils.robot | 2 Documentation This module provides general keywords for dump.
11 Create User Initiated Dump
12 [Documentation] Generate user initiated dump and return
13 ... the dump id number (e.g., "5"). Optionally return EMPTY
14 ... if out of dump space.
18 # check_out_of_space If ${False}, a dump will be created and
22 # returned if out of dump space was
23 # detected when creating the dump.
27 ... Set Global Variable ${REST_DUMP_URI} /xyz/openbmc_project/dump/
34 ... Run Keyword And Return Get The Dump Id ${resp}
[all …]
|
| /openbmc/linux/arch/powerpc/platforms/powernv/ |
| H A D | opal-dump.c | 3 * PowerNV OPAL Dump Interface
32 ssize_t (*show)(struct dump_obj *dump, struct dump_attribute *attr,
34 ssize_t (*store)(struct dump_obj *dump, struct dump_attribute *attr,
49 case 0x01: return "SP Dump"; in dump_type_to_string()
50 case 0x02: return "System/Platform Dump"; in dump_type_to_string()
51 case 0x03: return "SMA Dump"; in dump_type_to_string()
69 return sprintf(buf, "ack - acknowledge dump\n"); in dump_ack_show()
81 pr_warn("%s: Failed to send ack to Dump ID 0x%x (%d)\n", in dump_send_ack()
102 /* Attributes of a dump
103 * The binary attribute of the dump itself is dynamic
[all …]
|
| /openbmc/linux/net/bluetooth/ |
| H A D | coredump.c | 34 hci_dmp_cb(skb)->pkt_type, hdev->dump.state)
54 hdev->dump.state, state); in hci_devcd_update_state()
56 hdev->dump.state = state; in hci_devcd_update_state()
58 return hci_devcd_update_hdr_state(hdev->dump.head, in hci_devcd_update_state()
59 hdev->dump.alloc_size, state); in hci_devcd_update_state()
64 char dump_start[] = "--- Start dump ---\n"; in hci_devcd_mkheader()
72 if (hdev->dump.dmp_hdr) in hci_devcd_mkheader()
73 hdev->dump.dmp_hdr(hdev, skb); in hci_devcd_mkheader()
83 if (hdev->dump.notify_change) in hci_devcd_notify()
84 hdev->dump.notify_change(hdev, state); in hci_devcd_notify()
[all …]
|
| /openbmc/linux/drivers/net/wireless/mediatek/mt76/mt7915/ |
| H A D | coredump.c | 12 MODULE_PARM_DESC(coredump_memdump, "Optional ability to dump firmware memory");
144 mt7915_coredump_fw_state(struct mt7915_dev *dev, struct mt7915_coredump *dump, in mt7915_coredump_fw_state() argument
157 strscpy(dump->fw_state, "normal", sizeof(dump->fw_state)); in mt7915_coredump_fw_state()
159 strscpy(dump->fw_state, "assert", sizeof(dump->fw_state)); in mt7915_coredump_fw_state()
161 strscpy(dump->fw_state, "exception", sizeof(dump->fw_state)); in mt7915_coredump_fw_state()
167 mt7915_coredump_fw_trace(struct mt7915_dev *dev, struct mt7915_coredump *dump, in mt7915_coredump_fw_trace() argument
173 dump->last_msg_id = mt76_rr(dev, MT_FW_LAST_MSG_ID); in mt7915_coredump_fw_trace()
178 dump->eint_info_idx = n; in mt7915_coredump_fw_trace()
183 dump->irq_info_idx = n; in mt7915_coredump_fw_trace()
188 dump->sched_info_idx = n; in mt7915_coredump_fw_trace()
[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>.
14 Method to create a manual Dump.
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
25 in the format 'domain.Dump.Create.CreateParameters.ParamName'.
39 dump
43 - xyz.openbmc_project.Dump.Create.Error.Disabled
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/ |
| H A D | Notify.interface.yaml | 2 Implement to notify the creation of new dump. This interface is used when a
3 dump is already created and ready to be offloaded. This interface will
4 update an existing dump object or add a new one with the provided
6 being collected and the dump needs to be packaged.
9 the host. Post dump completion, the host notifies via PLDM, which calls this
10 interface with dump type, dump source id (an id assigned by the host and
12 dump.
15 com.ibm.Dump.Notify on /xyz/openbmc_project/dump.
19 Create or update a dump entry based on the parameters and the specific
20 dump type.
[all …]
|
| H A D | Create.interface.yaml | 2 Implement this to pass additional parameters to the create dump. Each
3 required parameter for the dump in the ibm domain should be added here as an
9 Additional parameters for creating the dump.
13 The resource dump is collected from various host resources. The
14 resource to collect the dump is indicated by using the resource
16 host to generate a resource dump.
19 The password for authenticating the resource dump request.
23 dump. The value should be a 32 bit unsigned integer.
26 Type of the dump to be collected
29 A unique id of failing hardware unit which is causing the dump.
[all …]
|
| /openbmc/phosphor-debug-collector/ |
| H A D | bmc_dump_entry.hpp | 4 #include "xyz/openbmc_project/Dump/Entry/BMC/server.hpp"
5 #include "xyz/openbmc_project/Dump/Entry/server.hpp"
16 namespace dump namespace
24 sdbusplus::xyz::openbmc_project::Dump::Entry::server::BMC>;
30 * @brief OpenBMC Dump Entry implementation.
32 * xyz.openbmc_project.Dump.Entry DBus API
34 class Entry : virtual public phosphor::dump::Entry, virtual public EntryIfaces
44 /** @brief Constructor for the Dump Entry Object
47 * @param[in] dumpId - Dump id.
48 * @param[in] timeStamp - Dump creation timestamp
[all …]
|
| H A D | dump_manager_bmc.hpp | 9 #include <xyz/openbmc_project/Dump/Create/server.hpp>
16 namespace dump namespace
22 sdbusplus::xyz::openbmc_project::Dump::server::Create>;
24 using UserMap = phosphor::dump::inotify::UserMap;
26 using Watch = phosphor::dump::inotify::Watch;
30 * @brief OpenBMC Dump manager implementation.
32 * xyz.openbmc_project.Dump.Create DBus API
36 virtual public phosphor::dump::Manager
48 * @param[in] event - Dump manager sd_event loop.
50 * @param[in] baseEntryPath - Base path for dump entry.
[all …]
|
| H A D | meson.options | 10 value : 'xyz.openbmc_project.Dump.Manager',
15 value : '/xyz/openbmc_project/dump',
16 description : 'The dump manager D-Bus root'
20 value : '/xyz/openbmc_project/dump/bmc',
21 description : 'The BMC dump manager D-Bus object path'
30 value : '/xyz/openbmc_project/dump/bmc/entry',
31 description : 'The BMC dump entry D-Bus object path'
46 description : 'Maximum size of one bmc dump in kilo bytes'
51 description : 'Minimum space required for one bmc dump in kilo bytes'
56 description : 'Total size of the dump in kilo bytes'
[all …]
|
| /openbmc/openpower-debug-collector/dump/tools/common/include/ |
| H A D | gendumpheader | 3 #Header for BMC DUMP
5 #This script will generate generic IBM dump header format.
7 #Note: The dump header will be imposed on the dump file i.e
8 #<dump name>.tar.xz/gz only on IBM specific systems, user needs to
9 #separate out the header before extracting the dump.
18 #Dump Summary size without header
67 #Function to fetch the size of the dump
69 #Adding 516 bytes as the total dump size is dump tar size
70 #plus the dump header entry in this case
90 #Function to set dump id to 8 bytes format
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/Entry/ |
| H A D | System.interface.yaml | 2 Implement this to add system dump management.
4 System dumps are dump of the host memory and hardware states generated
5 during a failure in the host firmware. This can be a huge dump stored in the
6 host memory, the BMC doesn't store this dump but stream this dump to an
8 system dump, users can also request for this kind of dump.
14 The dump id provided by the source of the dump. There are dumps which
15 get generated outside the BMC, like a system dump which gets generated
17 when communicating to the source of the dump the SourceDumpId will be
23 dump outside of the BMC. This token can be used to identify the dump
31 dump, alters the system state. This kind of dump is typically
[all …]
|
| /openbmc/phosphor-debug-collector/dump-extensions/openpower-dumps/ |
| H A D | resource_dump_entry.hpp | 3 #include "com/ibm/Dump/Entry/Resource/server.hpp"
13 namespace dump namespace
21 sdbusplus::com::ibm::Dump::Entry::server::Resource>;
29 * @brief Resource Dump Entry implementation.
30 * @details An extension to Dump::Entry class and
32 * com::ibm::Dump::Entry::Resource DBus API
34 class Entry : virtual public phosphor::dump::Entry, virtual public EntryIfaces
44 /** @brief Constructor for the resource dump Entry Object
47 * @param[in] dumpId - Dump id.
48 * @param[in] timeStamp - Dump creation timestamp
[all …]
|
| H A D | system_dump_entry.hpp | 4 #include "xyz/openbmc_project/Dump/Entry/System/server.hpp"
11 namespace dump namespace
19 sdbusplus::xyz::openbmc_project::Dump::Entry::server::System>;
27 * @brief System Dump Entry implementation.
29 * xyz.openbmc_project.Dump.Entry DBus API
31 class Entry : virtual public phosphor::dump::Entry, virtual public EntryIfaces
41 /** @brief Constructor for the Dump Entry Object
44 * @param[in] dumpId - Dump id.
45 * @param[in] timeStamp - Dump creation timestamp
47 * @param[in] dumpSize - Dump size in bytes.
[all …]
|
| H A D | dump_manager_system.hpp | 5 #include "xyz/openbmc_project/Dump/NewDump/server.hpp"
9 #include <xyz/openbmc_project/Dump/Create/server.hpp>
13 namespace dump namespace
20 sdbusplus::xyz::openbmc_project::Dump::server::Create,
21 sdbusplus::xyz::openbmc_project::Dump::server::NewDump>;
24 * @brief System Dump manager implementation.
26 * xyz.openbmc_project.Dump.Notify DBus API
30 virtual public phosphor::dump::Manager
42 * @param[in] event - Dump manager sd_event loop.
44 * @param[in] baseEntryPath - Base path of the dump entry.
[all …]
|
| H A D | dump_manager_resource.hpp | 4 #include "xyz/openbmc_project/Dump/NewDump/server.hpp"
6 #include <com/ibm/Dump/Create/server.hpp>
9 #include <xyz/openbmc_project/Dump/Create/server.hpp>
13 namespace dump namespace
20 sdbusplus::xyz::openbmc_project::Dump::server::Create,
21 sdbusplus::com::ibm::Dump::server::Create,
22 sdbusplus::xyz::openbmc_project::Dump::server::NewDump>;
25 * @brief Resource Dump manager implementation.
27 * xyz.openbmc_project.Dump.Notify and
28 * xyz.openbmc_project.Dump.Create DBus APIs
[all …]
|
| /openbmc/openpower-debug-collector/dump/ |
| H A D | sbe_dump_collector.hpp | 20 namespace openpower::dump::sbe_chipop namespace
51 * involves identifying available processors, initiating the dump
52 * collection process, and managing the collected dump files.
54 * @param type The type of dump to collect.
55 * @param id A unique identifier for the dump collection operation.
56 * @param failingUnit The identifier of the failing unit prompting the dump
65 * @brief Collects a dump from a single SBE.
68 * dump from the specified SBE.
71 * @param path The filesystem path where the dump should be stored.
72 * @param id The unique identifier for this dump collection operation.
[all …]
|
| H A D | dump_monitor.hpp | 13 #include <xyz/openbmc_project/Dump/Entry/System/common.hpp>
19 namespace openpower::dump namespace
27 * @brief Monitors DBus signals for dump creation and handles them.
34 * Initializes the DBus connection and signal match for monitoring dump
41 "/xyz/openbmc_project/dump") + in DumpMonitor()
43 "xyz.openbmc_project.Dump.Manager"), in DumpMonitor()
59 /* @brief Monitores dump interfaces */
61 "com.ibm.Dump.Entry.Hardware", "com.ibm.Dump.Entry.Hostboot",
62 "com.ibm.Dump.Entry.SBE", "xyz.openbmc_project.Dump.Entry.System"};
68 * @brief Handles the received DBus signal for dump creation.
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | dump.json | 8 # = Dump guest memory
14 # An enumeration of guest-memory-dump's format.
49 # @dump-guest-memory:
51 # Dump guest's memory to vmcore. It is a synchronous operation that
79 # for the dump to finish. The user can track progress using
80 # "query-dump". (since 2.6).
85 # to dump all guest's memory, please specify the start @begin and
88 # @format: if specified, the format of guest memory dump. But non-elf
99 # -> { "execute": "dump-guest-memory",
100 # "arguments": { "paging": false, "protocol": "fd:dump" } }
[all …]
|
| /openbmc/linux/drivers/net/wireless/mediatek/mt76/mt7996/ |
| H A D | coredump.c | 12 MODULE_PARM_DESC(coredump_memdump, "Optional ability to dump firmware memory");
101 mt7996_coredump_fw_state(struct mt7996_dev *dev, struct mt7996_coredump *dump, in mt7996_coredump_fw_state() argument
110 strscpy(dump->fw_state, "normal", sizeof(dump->fw_state)); in mt7996_coredump_fw_state()
112 strscpy(dump->fw_state, "exception", sizeof(dump->fw_state)); in mt7996_coredump_fw_state()
118 mt7996_coredump_fw_stack(struct mt7996_dev *dev, struct mt7996_coredump *dump, in mt7996_coredump_fw_stack() argument
123 strscpy(dump->pc_current, "program counter", sizeof(dump->pc_current)); in mt7996_coredump_fw_stack()
131 dump->pc_stack[0] = mt76_rr(dev, MT_CONN_DBG_CTL_PC_LOG); in mt7996_coredump_fw_stack()
143 dump->pc_stack[i + 1] = in mt7996_coredump_fw_stack()
151 dump->lr_stack[i] = in mt7996_coredump_fw_stack()
165 struct mt7996_coredump *dump; in mt7996_coredump_build() local
[all …]
|
| /openbmc/openpower-debug-collector/ |
| H A D | .shellcheck-ignore | 1 dump/tools/bmcdump/plugins/badpel
2 dump/tools/bmcdump/plugins/cfam
3 dump/tools/bmcdump/plugins/dumpfilelist
4 dump/tools/bmcdump/plugins/guardlist
5 dump/tools/bmcdump/plugins/obmcconsole1
6 dump/tools/bmcdump/plugins/occ
7 dump/tools/bmcdump/plugins/pels
8 dump/tools/bmcdump/plugins/phal_devtree
9 dump/tools/bmcdump/plugins/vpd_data
10 dump/tools/bmcdump/plugins/faultlog
[all …]
|