| /openbmc/linux/drivers/target/iscsi/ |
| H A D | iscsi_target_datain_values.c | 76 * For Normal and Recovery DataSequenceInOrder=Yes and DataPDUInOrder=Yes.
90 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()
174 * For Normal and Recovery DataSequenceInOrder=No and DataPDUInOrder=Yes.
[all …]
|
| /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
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | remoteproc_sysfs.c | 22 * By writing to the 'recovery' sysfs entry, we control the behavior of the
23 * recovery mechanism dynamically. The default value of this entry is "enabled".
25 * The 'recovery' sysfs entry supports these commands:
29 * processor crashes while recovery is disabled, it will
30 * be automatically recovered too as soon as recovery is enabled.
36 * recover: This function will trigger an immediate recovery if the
38 * or checking the recovery state (enabled/disabled).
40 * additional crashes to happen after enabling recovery. In this
41 * case, enabling recovery will make it hard to debug subsequent
42 * crashes, so it's recommended to keep recovery disabled, and
[all …]
|
| H A D | remoteproc_debugfs.c | 61 * disabled: By default coredump collection is disabled. Recovery will
68 * recovery process will have to wait until data is read by
174 /* expose recovery flag via debugfs */
185 * By writing to the 'recovery' debugfs entry, we control the behavior of the
186 * recovery mechanism dynamically. The default value of this entry is "enabled".
188 * The 'recovery' debugfs entry supports these commands:
192 * processor crashes while recovery is disabled, it will
193 * be automatically recovered too as soon as recovery is enabled.
199 * recover: This function will trigger an immediate recovery if the
201 * or checking the recovery state (enabled/disabled).
[all …]
|
| /openbmc/linux/fs/ocfs2/dlm/ |
| H A D | dlmrecovery.c | 5 * recovery stuff
127 /* Worker function used during recovery. */
164 * RECOVERY THREAD
169 /* wake the recovery thread in dlm_kick_recovery_thread()
171 * 1) sleeping with no recovery happening in dlm_kick_recovery_thread()
172 * 2) sleeping with recovery mastered elsewhere in dlm_kick_recovery_thread()
173 * 3) recovery mastered here, waiting on reco data */ in dlm_kick_recovery_thread()
178 /* Launch the recovery thread */
181 mlog(0, "starting dlm recovery thread...\n"); in dlm_launch_recovery_thread()
197 mlog(0, "waiting for dlm recovery thread to exit\n"); in dlm_complete_recovery_thread()
[all …]
|
| /openbmc/linux/drivers/s390/scsi/ |
| H A D | zfcp_dbf.h | 28 * struct zfcp_dbf_rec_trigger - trace record for triggered recovery action
29 * @ready: number of ready recovery actions
30 * @running: number of running recovery actions
31 * @want: wanted recovery action
32 * @need: needed recovery action
42 * struct zfcp_dbf_rec_running - trace record for running recovery
45 * @rec_step: current step of the recovery action
58 * enum zfcp_dbf_rec_id - recovery trace record id
59 * @ZFCP_DBF_REC_TRIG: triggered recovery identifier
60 * @ZFCP_DBF_REC_RUN: running recovery identifier
[all …]
|
| H A D | zfcp_def.h | 94 * @ZFCP_ERP_ACTION_REOPEN_LUN: LUN recovery.
95 * @ZFCP_ERP_ACTION_REOPEN_PORT: Port recovery.
96 * @ZFCP_ERP_ACTION_REOPEN_PORT_FORCED: Forced port recovery.
97 * @ZFCP_ERP_ACTION_REOPEN_ADAPTER: Adapter recovery.
130 u32 status; /* recovery status */
176 struct list_head erp_ready_head; /* error recovery for this
182 struct zfcp_erp_action erp_action; /* pending error recovery */
219 struct zfcp_erp_action erp_action; /* pending error recovery */
261 * running I/O and recovery is in struct zfcp_scsi_dev.
|
| /openbmc/linux/Documentation/PCI/ |
| H A D | pci-error-recovery.rst | 4 PCI Error Recovery
26 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
[all …]
|
| H A D | pcieaer-howto.rst | 43 - 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/fs/gfs2/ |
| H A D | lock_dlm.c | 20 #include "recovery.h"
349 * dlm/gfs2 recovery coordination using dlm_recover callbacks
355 * 4. dlm_controld starts and finishes its own user level recovery
356 * 5. dlm_controld starts dlm-kernel dlm_recoverd to do kernel recovery
358 * 7. dlm_recoverd does its own lock recovery
364 * 13. gfs2_recover provides recovery results to gfs2_control (recovery_result)
368 * - failures during recovery
395 * - parallel recovery steps across all nodes
410 * and missing a journal recovery?
421 * require recovery, because the mount in step 4 could not have
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-remoteproc | 83 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/Documentation/networking/devlink/ |
| H A D | devlink-health.rst | 23 attributes of the health reporting and recovery procedures.
33 * 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/arch/ia64/lib/ |
| H A D | strlen.S | 17 * 09/24/99 S.Eranian add speculation recovery code
39 // settings of the DCR register, we provide recovery code in case
40 // speculation fails. The recovery code is going to "redo" the work using
50 // It should be noted that we execute recovery code only when we need
52 // recovery code on pure read ahead data.
124 // We must return try the recovery code iff
132 (p6) br.cond.spnt .recover // jump to recovery if val1 is NaT
139 (p7) br.cond.spnt .recover // jump to recovery if val2 is NaT
154 // Outlined recovery code when speculation failed
193 br.ret.sptk.many rp // end of successful recovery code
|
| /openbmc/linux/include/linux/ |
| H A D | dm-region-hash.h | 87 * Region recovery control.
90 /* Prepare some regions for recovery by starting to quiesce them. */
93 /* Try fetching a quiesced region for recovery. */
96 /* Report recovery end on a region. */
99 /* Returns number of regions with recovery work outstanding. */
102 /* Start/stop recovery. */
|
| /openbmc/linux/include/linux/qed/ |
| H A D | qede_rdma.h | 53 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/fs/ocfs2/ |
| H A D | journal.c | 81 * offline slots during recovery and mount
206 /* disable any new recovery threads and wait for any currently in ocfs2_recovery_exit()
213 /* At this point, we know that no more recovery threads can be in ocfs2_recovery_exit()
214 * launched, so wait for any recovery completion work to in ocfs2_recovery_exit()
220 * Now that recovery is shut down, and the osb is about to be in ocfs2_recovery_exit()
924 /* Skip recovery waits here - journal inode metadata never in ocfs2_journal_init()
1289 /* Does the second half of the recovery process. By this point, the
1291 * hence it's no longer in the recovery map, but there's still some
1292 * cleanup we can do which shouldn't happen within the recovery thread
1296 * NOTE: This function can and will sleep on recovery of other nodes
[all …]
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | gpio-fault-injection.rst | 36 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/linux/net/ipv4/ |
| H A D | tcp_recovery.c | 11 * the recovery or starting the recovery by DUPACK threshold. in tcp_rack_reo_wnd()
131 * the aRTT term is bounded by the fast recovery or timeout, in tcp_rack_advance()
172 * triggering fast recovery, increment reo_wnd by min_rtt/4 (upper bounded
178 * recovery undo). After that, reset it to default (min_rtt/4).
212 /* RFC6582 NewReno recovery for non-SACK connection. It simply retransmits
214 * a) three or more DUPACKs to start the fast recovery
215 * b) an ACK acknowledging new data during the fast recovery.
|
| /openbmc/linux/drivers/md/ |
| H A D | md.c | 476 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in mddev_resume()
1382 /* active but not in sync implies recovery up to in super_90_validate()
1972 &mddev->recovery)) in super_1_validate()
2483 /* May as well allow recovery to be retried once */ in bind_rdev_to_array()
2680 * curr_resync_completed can only be used during recovery. in md_update_sb()
2687 test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) && in md_update_sb()
2688 test_bit(MD_RECOVERY_RECOVER, &mddev->recovery) && in md_update_sb()
2689 !test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in md_update_sb()
2737 * then a recovery will happen and soon that array won't in md_update_sb()
2823 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) in md_update_sb()
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | st,sta32x.txt | 44 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/pci/pcie/ |
| H A D | err.c | 3 * This file implements the error recovery as a core part of PCIe error
5 * collected and printed to console, then, an error recovery procedure
6 * will be executed by following the PCI error recovery rules.
208 * or RCiEP, recovery runs on the device itself. For Ports, that in pcie_do_recovery()
211 * If it was detected by another device (Endpoint, etc), recovery in pcie_do_recovery()
272 pci_info(bridge, "device recovery successful\n"); in pcie_do_recovery()
281 pci_info(bridge, "device recovery failed\n"); in pcie_do_recovery()
|
| /openbmc/linux/arch/s390/pci/ |
| H A D | pci_event.c | 87 pr_info("%s: Automatic recovery failed after initial reporting\n", pci_name(pdev)); in zpci_event_notify_error_detected()
112 pr_info("%s: Automatic recovery failed after MMIO re-enable\n", in zpci_event_do_error_state_clear()
147 pr_info("%s: Automatic recovery failed after slot reset\n", pci_name(pdev)); in zpci_event_do_reset()
157 * We follow the scheme outlined in Documentation/PCI/pci-error-recovery.rst.
158 * With the simplification that recovery always happens per function
170 * configuration space while we perform recovery. in zpci_event_attempt_error_recovery()
191 pr_info("%s: The %s driver bound to the device does not support error recovery\n", in zpci_event_attempt_error_recovery()
211 pr_err("%s: Automatic recovery failed; operator intervention is required\n", in zpci_event_attempt_error_recovery()
279 case 0x0040: /* Service Action or Error Recovery Failed */ in __zpci_event_error()
|
| /openbmc/linux/arch/powerpc/platforms/powernv/ |
| H A D | opal-hmi.c | 47 "Core checkstop during recovery" }, in print_core_checkstop_reason()
54 "Recovery in maintenance mode" }, in print_core_checkstop_reason()
64 "Hang Recovery Failed (core check stop)" }, in print_core_checkstop_reason()
203 "Processor Recovery done", in print_hmi_event_info()
204 "Processor recovery occurred again", in print_hmi_event_info()
205 "Processor recovery occurred for masked error", in print_hmi_event_info()
211 "SCOM has set a reserved FIR bit to cause recovery", in print_hmi_event_info()
212 "Debug trigger has set a reserved FIR bit to cause recovery", in print_hmi_event_info()
214 "CAPP recovery process is in progress", in print_hmi_event_info()
|