| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_dumps.robot | 34 ${dump_id}= Create User Initiated BMC Dump Via Redfish
39 Verify User Initiated BMC Dump When Host Powered Off
40 [Documentation] Create user initiated BMC dump at host off state and
45 ${dump_id}= Create User Initiated BMC Dump Via Redfish
51 Verify User Initiated BMC Dump Size
52 [Documentation] Verify user initiated BMC dump size is under 20 MB.
56 ${dump_id}= Create User Initiated BMC Dump Via Redfish
73 Verify Internal Failure Initiated BMC Dump Size
74 [Documentation] Verify that the internal failure initiated BMC dump size is under 20 MB.
105 Create User Initiated BMC Dump Via Redfish
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | OriginatedBy.interface.yaml | 8 Unique Id of the originator that initiated the respective operation.
17 Type of the originator that initiated the respective operation.
22 Indicates the type of the originator that initiated the operation.
26 Client of the service that initiated the operation.
29 A process running on the service initiated the operation.
33 service initiated the operation.
|
| /openbmc/openbmc-test-automation/openpower/mpipl/ |
| H A D | test_mpipl_basic.robot | 30 Trigger User Tool Initiated MPIPL
31 [Documentation] Trigger And Verify user tool initiated dump using
42 Trigger User Initiated MPIPL Using Redfish
49 Redfish Initiated MPIPL
85 Redfish Initiated MPIPL
|
| /openbmc/docs/designs/ |
| H A D | dump-manager.md | 53 include host memory and/or register data. This dump can be initiated by BMC and
61 A special type of host dump is initiated and collected by the host based on the
118 caller for the user-initiated dumps.
119 - An external request of dump is considered as a user-initiated BMC dump and
132 similar to user-initiated dumps with the following difference.
158 user-initiated dump.
|
| H A D | power-recovery.md | 88 user has initiated some form of manual reset which is detectable by the BMC as
89 being user initiated, the BMC software must:
93 - Log an error indicating a user initiated forced reset has occurred
142 - Tell the host firmware that it is a automated power-on recovery initiated boot
202 initiated a reset of the system).
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | Entry.interface.yaml | 14 The transfer will be initiated to the target provide. The caller of
17 transfer is successfully initiated. Once the transfer is completed.
|
| H A D | Create.interface.yaml | 61 Type of the originator that initiated the respective operation.
80 BMC dump is initiated as a response to a specific system event,
|
| /openbmc/openpower-hw-diags/test/ |
| H A D | test-root-cause-filter.cpp | 60 // MC_DSTL_FIR[1]: AFU initiated Recoverable Attn on Subchannel A in TEST()
99 // MC_DSTL_FIR[0]: AFU initiated Checkstop on Subchannel A in TEST()
128 // Test 5: Test a firmware initiated channel fail due to an IUE threshold on in TEST()
|
| /openbmc/openbmc-test-automation/redfish/systems/ |
| H A D | test_led_indicator_asserted.robot | 103 # LEDs after the lamp test is initiated (e.g. "Blinking")
133 # power supplies units are initiated (e.g. "Lit")
166 # LEDs after the lamp test is initiated (e.g. "Blinking")
184 # are initiated (e.g. "Lit")
|
| /openbmc/ipmitool/include/ipmitool/ |
| H A D | ipmi_sel.h | 404 …{ 0x0f, 0x01, 0x05, IPMI_EVENT_CLASS_DISCRETE, "System Firmware Hang", "User-initiated system setu…
418 { 0x0f, 0x01, 0x13, IPMI_EVENT_CLASS_DISCRETE, "System Firmware Hang", "System boot initiated" },
432 …{ 0x0f, 0x02, 0x05, IPMI_EVENT_CLASS_DISCRETE, "System Firmware Progress", "User-initiated system …
446 …{ 0x0f, 0x02, 0x13, IPMI_EVENT_CLASS_DISCRETE, "System Firmware Progress", "System boot initiated"…
510 { 0x1d, 0x00, 0xff, IPMI_EVENT_CLASS_DISCRETE, "System Boot Initiated", "Initiated by power up" },
511 …{ 0x1d, 0x01, 0xff, IPMI_EVENT_CLASS_DISCRETE, "System Boot Initiated", "Initiated by hard reset" …
512 …{ 0x1d, 0x02, 0xff, IPMI_EVENT_CLASS_DISCRETE, "System Boot Initiated", "Initiated by warm reset" …
513 …{ 0x1d, 0x03, 0xff, IPMI_EVENT_CLASS_DISCRETE, "System Boot Initiated", "User requested PXE boot" …
514 …{ 0x1d, 0x04, 0xff, IPMI_EVENT_CLASS_DISCRETE, "System Boot Initiated", "Automatic boot to diagnos…
515 …{ 0x1d, 0x05, 0xff, IPMI_EVENT_CLASS_DISCRETE, "System Boot Initiated", "OS initiated hard reset" …
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | redfish_code_update_utils.robot | 321 Create Initiated Task State Dict
359 ${task_inv}= Create Initiated Task State Dict ${task_payload}
376 …f '${task_payload['Payload']['TargetUri']}' == '${target_uri}' Create Initiated Task State Dict …
385 # target_uri Target URI for which task is initiated.
401 # task_inv Initiated task inventory dict information.
|
| H A D | tftp_update_utils.py | 29 Wait for the BMC to complete a previously initiated reboot.
|
| H A D | state_manager.robot | 256 ${session_active}= Check If BMC Reboot Is Initiated
262 Check If BMC Reboot Is Initiated
263 [Documentation] Checks whether BMC Reboot is initiated by checking
|
| H A D | dump_utils.robot | 11 Create User Initiated Dump
12 [Documentation] Generate user initiated dump and return
301 Create User Initiated BMC Dump Via Redfish
302 …[Documentation] Generate user initiated BMC dump via Redfish and return the dump id number (e.g.,…
442 [Documentation] Generate user initiated BMC dump via Redfish and return
|
| /openbmc/phosphor-host-ipmid/ |
| H A D | meson.options | 41 # initiated shutdown or reboot requests
46 description: 'Directory to store host initiated shutdown file',
52 description: 'File to create if host has initiated shutdown or reboot',
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | microvm.rst | 110 Triggering a guest-initiated shut down
118 The recommended way to trigger a guest-initiated shut down is by
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | configuration.md | 25 ## How configuration is initiated
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Multics | 14 was initiated by Massachusetts Institute of Technology Project MAC
|
| /openbmc/u-boot/board/aristainetos/ |
| H A D | nt5cc256m16cp.cfg | 34 /* in DDR3, 64-bit mode, only MMDC0 is initiated */
|
| H A D | mt41j128M.cfg | 36 /* in DDR3, 64-bit mode, only MMDC0 is initiated */
|
| /openbmc/u-boot/doc/ |
| H A D | README.arm-caches | 22 initiated.
|
| /openbmc/qemu/include/hw/i3c/ |
| H A D | remote-i3c.h | |
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | Resource.interface.yaml | 28 operations and ensure they are initiated only by authorized personnel,
|
| /openbmc/qemu/docs/devel/ |
| H A D | replay.rst | 270 initiated by the sender. Followed by:
294 initiated by qemu. Followed by:
299 initiated by qemu. Followed by:
|
| /openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-sequencing/files/ |
| H A D | gpios-manager.sh | 72 # If bit 10 is set Software initiated a shutdown we need to restart
|