| /openbmc/docs/designs/ |
| H A D | bmc-service-failure-debug-and-recovery.md | 1 # BMC Service Failure Debug and Recovery
22 recovery of a failed BMC.
40 recovery in the face of well-defined error conditions, but the need to mitigate
69 In the face of continued operation due to internal recovery a service restart is
156 #### Recovery Mechanisms
158 The ability for external consumers to control the recovery behaviour of BMC
163 | Severity | BMC Recovery Mechanism | Used for …
165 | 1 | Graceful reboot request | Normal circumstances or recovery from platform data provider…
166 | 2 | Forceful reboot request | Recovery from unresponsive platform data transport providers…
178 therefore limited to recovery of unresponsive in-band interfaces.
[all …]
|
| H A D | power-recovery.md | 1 # OpenBMC Server Power Recovery
11 Modern computer systems have a feature, automated power-on recovery, which in
18 There are also instances where the user may not want automatic power recovery to
31 recovery features. A brownout is a scenario where BMC firmware detects (or is
59 ### Automated Power-On Recovery
81 feature is a way for software to utilize automated power-on recovery function
85 ### BMC and System Recovery Paths
96 - Not implement any power recovery policy on the system
97 - Turn power recovery back on once BMC has a normal reboot
140 power-on recovery
[all …]
|
| H A D | bmc-reset-with-host-up.md | 71 taking recovery actions.
91 firmware and talking PLDM but the BMC recovery paths will differ based on
105 - Execute automated recovery of host if desired
113 recovery of the host.
122 ### Automated Recovery when host does not respond
134 - Move host to Quiesce and allow automated recovery to kick in
151 If the register is not `0xA5000001`, then the BMC will follow whatever recovery
184 scenario once it comes back from its reboot and takes the proper recovery
188 reboot. Ensure the BMC follows the defined recovery for the system in this
|
| H A D | redfish-resource-supplement-for-pfr.md | 127 3. Platform Firmware Recovery reasons: This is used to log the reason for last
128 platform firmware component recovery.
168 "Indicates the reason for last BMC firmware recovery.",
169 "BMC firmware recovery occurred due to %1.",
222 recovery mechanism using below URI.
225 1. Corrupt the BMC/BIOS etc... firmware and check Panic events and recovery
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/testdisk/ |
| H A D | testdisk_7.2.bb | 1 DESCRIPTION = "TestDisk is a free data recovery software primarily designed to help recover lost pa…
15 …a recovery software designed to recover lost files including video, documents and archives from Ha…
|
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | mmc-recovery.service | 2 Description=mmc recovery
8 SyslogIdentifier=mmc-recovery
|
| /openbmc/qemu/tests/qtest/migration/ |
| H A D | postcopy-tests.c | 90 migration_test_add("/migration/postcopy/recovery/plain", in migration_test_add_postcopy_smoke()
129 migration_test_add("/migration/postcopy/preempt/recovery/plain", in migration_test_add_postcopy()
133 "/migration/postcopy/recovery/double-failures/handshake", in migration_test_add_postcopy()
137 "/migration/postcopy/recovery/double-failures/reconnect", in migration_test_add_postcopy()
|
| /openbmc/u-boot/tools/ |
| H A D | mrvl_uart.sh | 13 # UART recovery downloader for Armada SoCs
46 echo -e "\nMarvell recovery image downloader for Armada SoC family."
50 echo -e "\tfile - recovery boot image for target download"
88 echo -e "Recovery will run at $fast_baudrate baud"
|
| /openbmc/openbmc-test-automation/network/ |
| H A D | test_cable_pull_recover.robot | 2 Documentation Verify the port recovery by simulating its disconnection.
32 Verify Network Interface Recovery
33 [Documentation] Test the recovery of the network interface that has been
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/fans/phosphor-pid-control/ |
| H A D | monitor-fan-sensor | 125 echo "Normal fan count below threshold. Attempting recovery..."
129 # Recheck after recovery
131 echo "Post-recovery normal fan count: $normal_count"
137 echo "Recovery successful. System is stable."
|
| /openbmc/u-boot/include/configs/ |
| H A D | display5.h | 94 "run recovery;" \
114 "echo '# RECOVERY SWUupdate #';" \
233 "altbootcmd=run recovery\0" \
260 "recovery=" \
261 "echo BOOT: RECOVERY: SWU;" \
308 "run recovery;" \
316 "run recovery;" \
|
| H A D | socfpga_vining_fpga.h | 52 * if button B is pressed, wait $bootdelay and boot recovery system
83 "-(rcvrfs)\0" /* Recovery */ \
159 "echo \"Booting recovery system\" ; " \
|
| /openbmc/u-boot/drivers/ddr/marvell/a38x/ |
| H A D | mv_ddr_spd.h | 187 unsigned char byte_30; /* min refresh recovery delay time (t rfc1 min), l-s-byte, mtb */
188 unsigned char byte_31; /* min refresh recovery delay time (t rfc1 min), m-s-byte, mtb */
189 unsigned char byte_32; /* min refresh recovery delay time (t rfc2 min), l-s-byte, mtb */
190 unsigned char byte_33; /* min refresh recovery delay time (t rfc2 min), m-s-byte, mtb */
191 unsigned char byte_34; /* min refresh recovery delay time (t rfc4 min), l-s-byte, mtb */
192 unsigned char byte_35; /* min refresh recovery delay time (t rfc4 min), m-s-byte, mtb */
213 unsigned char byte_42; /* min write recovery time (t wr min) */
|
| /openbmc/openbmc/meta-ibm/meta-sbp1/recipes-phosphor/flash/phosphor-software-manager/ |
| H A D | bios-update.sh | 12 # me address, 0x2e oen, 0x00 - lun, 0xdf - force recovery
85 # Set ME to recovery mode
86 echo "Set ME to recovery mode"
|
| /openbmc/openbmc/meta-arm/kas/ |
| H A D | corstone1000-image-configuration.yml | 18 INITRAMFS_IMAGE:firmware ?= "corstone1000-recovery-image"
19 IMAGE_FSTYPES:firmware:pn-corstone1000-recovery-image = "${INITRAMFS_FSTYPES}"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/ddrescue/ |
| H A D | ddrescue_1.29.1.bb | 1 SUMMARY = "Data recovery tool"
2 DESCRIPTION = "GNU ddrescue is a data recovery tool. It copies data \
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc.json | 116 "Description": "Indicates the reason for BIOS firmware recovery.",
117 "Message": "BIOS firmware recovery occurred due to %1.",
152 "Description": "Indicates BIOS Recovery has completed.",
153 "Message": "BIOS Recovery Complete.",
160 "Description": "Indicates BIOS Recovery has started.",
161 "Message": "BIOS Recovery Start.",
186 "Description": "Indicates the reason for last BMC firmware recovery.",
187 "Message": "BMC firmware recovery occurred due to %1.",
221 "Description": "Indicates the reason for CPLD firmware recovery.",
222 "Message": "CPLD firmware recovery occurred due to %1.",
[all …]
|
| H A D | openbmc_message_registry.hpp | 184 "Indicates the reason for BIOS firmware recovery.",
185 "BIOS firmware recovery occurred due to %1.",
234 "Indicates BIOS Recovery has completed.",
235 "BIOS Recovery Complete.",
244 "Indicates BIOS Recovery has started.",
245 "BIOS Recovery Start.",
279 "Indicates the reason for last BMC firmware recovery.",
280 "BMC firmware recovery occurred due to %1.",
325 "Indicates the reason for CPLD firmware recovery.",
326 "CPLD firmware recovery occurred due to %1.",
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-system1/recipes-phosphor/flash/phosphor-software-manager/ |
| H A D | bios-update.sh | 31 # me address, 0x2e oen, 0x00 - lun, 0xdf - force recovery
60 # Set ME to recovery mode
61 echo "Set ME to recovery mode"
|
| /openbmc/openbmc/meta-ampere/meta-jefferson/recipes-ampere/platform/ampere-platform-init/ |
| H A D | ampere_platform_init.sh | 71 gpioset $(gpiofind hpm-fw-recovery)=0 # Force HPM FPGA recovery
74 gpioset $(gpiofind cpu-bios-recover)=0 # BIOS recovery enable from BMC
|
| /openbmc/u-boot/board/sbc8641d/ |
| H A D | README | 33 booting, or for U-Boot backup and recovery. A two pin jumper on the
37 a recently installed non-functional image, to perform a recovery from
|
| /openbmc/u-boot/include/ |
| H A D | ddr_spd.h | 34 unsigned char write_lat; /* 20 Write Latency (aka Write Recovery) */
115 unsigned char twr; /* 36 Write Recovery time tWR */
198 unsigned char twr_min; /* 17 Min Write REcovery Time */
208 unsigned char trfc_min_lsb; /* 24 Min Refresh Recovery Delay Time */
209 unsigned char trfc_min_msb; /* 25 Min Refresh Recovery Delay Time */
323 uint8_t trfc1_min_lsb; /* 30 Min Refresh Recovery Delay Time */
324 uint8_t trfc1_min_msb; /* 31 Min Refresh Recovery Delay Time */
325 uint8_t trfc2_min_lsb; /* 32 Min Refresh Recovery Delay Time */
326 uint8_t trfc2_min_msb; /* 33 Min Refresh Recovery Delay Time */
327 uint8_t trfc4_min_lsb; /* 34 Min Refresh Recovery Delay Time */
[all …]
|
| /openbmc/pldm/oem/meta/event/ |
| H A D | types.hpp | 183 {"PCIe DPC Event", "PCIe LER Event", "PCIe Link Retraining and Recovery",
191 "Memory SMBus hang recovery", "No DIMM in System", "CXL POST PPR event",
209 "COR Phy Lane failure, recovery in x8 width", "Reserved"});
|
| /openbmc/u-boot/drivers/video/ |
| H A D | logicore_dp_tx.c | 43 * @TS_CLOCK_RECOVERY: State for clock recovery
192 * bytes correspond to the lane status associated with clock recovery, channel
1027 /* delay for the clock recovery phase. */ in get_training_delay()
1197 * check_clock_recovery() - Check clock recovery success
1199 * @lane_count: The number of lanes for which to check clock recovery success
1202 * that the clock recovery sequence during link training was successful - the
1203 * RX device's link clock and data recovery unit has realized and maintained
1206 * Return: 0 if clock recovery was successful on all lanes in question, -ve if
1230 /* All (lane_count) lanes have achieved clock recovery. */ in check_clock_recovery()
1367 * training_state_clock_recovery() - Run clock recovery part of link training
[all …]
|
| /openbmc/phosphor-power/phosphor-chassis-power/ |
| H A D | README.md | 8 systems to handle chassis-level fault monitoring and recovery. The application
|