Home
last modified time | relevance | path

Searched refs:recovery (Results 1 – 25 of 340) sorted by relevance

12345678910>>...14

/openbmc/linux/drivers/target/iscsi/
H A Discsi_target_datain_values.c90 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_yes_and_yes()
98 next_burst_len = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
100 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
136 datain->data_sn = (!dr->recovery) ? cmd->data_sn++ : dr->data_sn++; in iscsit_set_datain_values_yes_and_yes()
139 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
147 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
157 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes()
164 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes()
189 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_no_and_yes()
197 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_no_and_yes()
[all …]
/openbmc/linux/include/linux/qed/
H A Dqede_rdma.h53 int qede_rdma_dev_add(struct qede_dev *dev, bool recovery);
56 void qede_rdma_dev_remove(struct qede_dev *dev, bool recovery);
62 bool recovery) in qede_rdma_dev_add() argument
70 bool recovery) {} in qede_rdma_dev_remove() argument
/openbmc/linux/drivers/md/
H A Dmd.c476 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in mddev_resume()
1980 &mddev->recovery)) in super_1_validate()
2695 test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) && in md_update_sb()
2696 test_bit(MD_RECOVERY_RECOVER, &mddev->recovery) && in md_update_sb()
2697 !test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in md_update_sb()
2831 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) in md_update_sb()
2873 set_bit(MD_RECOVERY_RECOVER, &mddev->recovery); in add_bound_rdev()
2874 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in add_bound_rdev()
3023 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in state_store()
3061 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in state_store()
[all …]
H A Ddm-raid.c3239 set_bit(MD_RECOVERY_FROZEN, &rs->md.recovery); in raid_ctr()
3359 static enum sync_state decipher_sync_action(struct mddev *mddev, unsigned long recovery) in decipher_sync_action() argument
3361 if (test_bit(MD_RECOVERY_FROZEN, &recovery)) in decipher_sync_action()
3365 if (!test_bit(MD_RECOVERY_DONE, &recovery) && in decipher_sync_action()
3366 (test_bit(MD_RECOVERY_RUNNING, &recovery) || in decipher_sync_action()
3367 (!mddev->ro && test_bit(MD_RECOVERY_NEEDED, &recovery)))) { in decipher_sync_action()
3368 if (test_bit(MD_RECOVERY_RESHAPE, &recovery)) in decipher_sync_action()
3371 if (test_bit(MD_RECOVERY_SYNC, &recovery)) { in decipher_sync_action()
3372 if (!test_bit(MD_RECOVERY_REQUESTED, &recovery)) in decipher_sync_action()
3374 if (test_bit(MD_RECOVERY_CHECK, &recovery)) in decipher_sync_action()
[all …]
H A Draid10.c144 if (test_bit(MD_RECOVERY_SYNC, &conf->mddev->recovery) || in r10buf_pool_alloc()
145 test_bit(MD_RECOVERY_RESHAPE, &conf->mddev->recovery)) in r10buf_pool_alloc()
191 &conf->mddev->recovery)) { in r10buf_pool_alloc()
483 &rdev->mddev->recovery); in raid10_end_write_request()
1095 if (!test_bit(MD_RECOVERY_RESHAPE, &rdev->mddev->recovery) || in choose_data_offset()
1148 while (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in regular_request_wait()
1433 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in raid10_write_request()
1654 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery)) in raid10_handle_discard()
1667 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery)) in raid10_handle_discard()
2033 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in raid10_error()
[all …]
/openbmc/linux/Documentation/networking/devlink/
H A Ddevlink-health.rst23 attributes of the health reporting and recovery procedures.
50 * Auto recovery attempt is being done. Depends on:
52 - Auto-recovery configuration
80 * Configure reporter's generic parameters (like: disable/enable auto recovery)
81 * Invoke recovery procedure
95 - Triggers reporter's recovery procedure.
98 event in terms of recovery flow should follow closely that of a real
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-remoteproc83 copy the dump. Also recovery process will not proceed until
86 What: /sys/class/remoteproc/.../recovery
89 Description: Remote processor recovery mechanism
91 Reports the recovery mechanism of the remote processor,
99 processor crashes while recovery is disabled, it will
100 be automatically recovered too as soon as recovery is enabled.
/openbmc/linux/drivers/net/wireless/ath/ath6kl/
H A Drecovery.c100 struct ath6kl_fw_recovery *recovery = &ar->fw_recovery; in ath6kl_recovery_init() local
103 INIT_WORK(&recovery->recovery_work, ath6kl_recovery_work); in ath6kl_recovery_init()
104 recovery->seq_num = 0; in ath6kl_recovery_init()
105 recovery->hb_misscnt = 0; in ath6kl_recovery_init()
/openbmc/linux/Documentation/PCI/
H A Dpci-error-recovery.rst26 of a bus disconnection, and then performing error recovery.
29 Reporting and recovery is performed in several steps. First, when
38 Next, recovery is performed in several stages. Most of the complexity
57 through a large number of contortions to complete recovery. Almost all
61 device drivers already handle very similar recovery procedures;
72 The error recovery API support is exposed to the driver in the form of
75 and the actual recovery steps taken are platform dependent. The
111 is assumed that the driver is not doing any direct recovery and requires
160 particular, if the platform doesn't isolate slots), and recovery
164 then recovery proceeds to STEP 4 (Slot Reset).
[all …]
H A Dpcieaer-howto.rst43 - Performs error recovery actions.
98 To enable error recovery, a software driver must provide callbacks.
152 PCI error-recovery callbacks
157 when performing error recovery actions.
162 pci-error-recovery.rst except PCIe-specific parts (e.g.
163 reset_link). Please refer to pci-error-recovery.rst for detailed
174 require any recovery actions. The AER driver clears the device's
200 function. If reset_link is not NULL, recovery function will use it
210 error recovery handler (pci_driver->err_handler is equal to NULL)?
222 Fatal error recovery will fail if the errors are reported by the
[all …]
/openbmc/linux/tools/testing/selftests/drivers/net/bonding/
H A DMakefile9 mode-1-recovery-updelay.sh \
10 mode-2-recovery-updelay.sh \
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dst,sta32x.txt44 If present, thermal warning recovery is enabled.
46 - st,fault-detect-recovery:
47 If present, fault detect recovery is enabled.
52 - st,fault-detect-recovery:
53 If present, then fault recovery will be enabled.
/openbmc/linux/drivers/ata/
H A Dpata_cs5520.c40 int recovery; member
70 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
75 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
79 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
/openbmc/docs/designs/
H A Dbmc-service-failure-debug-and-recovery.md22 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
158 The ability for external consumers to control the recovery behaviour of BMC
165 | 1 | Graceful reboot request | Normal circumstances or recovery from platform data provider…
178 therefore limited to recovery of unresponsive in-band interfaces.
197 needs an interface to the BMC that is dedicated to the role of BMC recovery,
207 recovery message from the host
211 1. The host has some indication that the recovery process has been activated
216 1. The host make use of a timeout to escalate to recovery mechanism 3 as it's
[all …]
H A Dpower-recovery.md11 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
81 feature is a way for software to utilize automated power-on recovery function
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
141 - Not run any power-on recovery logic when a brownout is occurring
142 - Tell the host firmware that it is a automated power-on recovery initiated boot
158 - Not execute any automated power-on recovery logic to prevent power on/off
[all …]
H A Dbmc-reset-with-host-up.md71 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.
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
/openbmc/linux/arch/arm64/boot/dts/marvell/
H A Darmada-3720-uDPU.dts23 i2c1_recovery_pins: i2c1-recovery-pins {
31 pinctrl-names = "default", "recovery";
/openbmc/linux/Documentation/i2c/
H A Dgpio-fault-injection.rst36 master under test should detect this condition and trigger a bus recovery (see
38 core (see 'struct bus_recovery_info'). However, the bus recovery will not
47 device. Bus recovery should be able to fix these situations. But please note:
51 and will init a bus recovery on its own. If you want to implement bus recovery
64 recovery. This time, however, it should succeed and the device should release
82 This is why bus recovery (up to 9 clock pulses) must either check SDA or send
/openbmc/openbmc/meta-ampere/meta-jefferson/recipes-ampere/platform/ampere-utils/
H A Dampere_firmware_upgrade.sh94 gpioset $(gpiofind hpm-fw-recovery)=1
98 gpioset $(gpiofind hpm-fw-recovery)=0
/openbmc/linux/drivers/net/ethernet/qlogic/qede/
H A Dqede_rdma.c86 int qede_rdma_dev_add(struct qede_dev *edev, bool recovery) in qede_rdma_dev_add() argument
94 if (recovery) in qede_rdma_dev_add()
116 void qede_rdma_dev_remove(struct qede_dev *edev, bool recovery) in qede_rdma_dev_remove() argument
122 if (!recovery) { in qede_rdma_dev_remove()
/openbmc/openbmc/meta-ampere/meta-mitchell/recipes-ampere/platform/ampere-utils/
H A Dampere_firmware_upgrade.sh114 gpioset $(gpiofind hpm-fw-recovery)=1
118 gpioset $(gpiofind hpm-fw-recovery)=0
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/ddrescue/
H A Dddrescue_1.29.bb1 SUMMARY = "Data recovery tool"
2 DESCRIPTION = "GNU ddrescue is a data recovery tool. It copies data \
/openbmc/linux/drivers/i2c/busses/
H A Di2c-uniphier.c161 bool recovery = false; in uniphier_i2c_master_xfer_one() local
175 recovery = true; in uniphier_i2c_master_xfer_one()
183 recovery = true; in uniphier_i2c_master_xfer_one()
188 if (recovery) in uniphier_i2c_master_xfer_one()
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-devices-node198 ignored by memory error recovery attempt, usually because
200 gives up the recovery.
207 failed by memory error recovery attempt. This usually means
208 a key recovery operation failed.
215 delayed by memory error recovery attempt. Delayed poisoned
223 recovered by memory error recovery attempt.
/openbmc/linux/Documentation/admin-guide/
H A Dfilesystem-monitoring.rst13 sysadmin, start recovery) when a file system problem is detected.
20 early file system problem detection and reporting recovery tools.
76 specific application can use that information to attempt a recovery

12345678910>>...14