Searched full:recovery (Results 1 – 25 of 128) sorted by relevance
123456
| /Documentation/ABI/testing/ |
| 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.
|
| D | sysfs-driver-chromeos-acpi | 9 0 Read only (recovery) firmware.
21 0 Recovery.
37 2 Recovery button was pressed.
38 4 Recovery button was pressed (EC firmware).
76 1 Recovery button.
|
| /Documentation/PCI/ |
| 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 …]
|
| 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 …]
|
| D | index.rst | 17 pci-error-recovery
|
| /Documentation/networking/devlink/ |
| 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
|
| D | sfc.rst | 47 * - ``coproc.recovery``
49 - SmartNIC application co-processor (APU) recovery operating system version.
|
| /Documentation/devicetree/bindings/sound/ |
| 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.
|
| D | cs35l32.txt | 39 - cirrus,battery-recovery : Low battery nominal recovery threshold, rising VP.
|
| /Documentation/i2c/ |
| 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
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | reboot-mode.yaml | 24 - recovery: Android Recovery mode, it is a mode to format the device or update a new image.
45 mode-recovery = <1>;
|
| /Documentation/devicetree/bindings/misc/ |
| D | xlnx,tmr-inject.yaml | 16 recovery logic is working properly.
31 recovery.
|
| D | xlnx,tmr-manager.yaml | 14 TMR subsystem state, including fault detection and error recovery. The core
31 recovery.
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 13 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
|
| /Documentation/filesystems/ |
| D | gfs2-uevents.rst | 45 of journal recovery for one of the filesystems journals. It has
47 has just been recovered, and RECOVERY=[Done|Failed] to indicate the
51 recovery via the /sys/fs/gfs2/<fsname>/lock_module/recovery file.
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 18 control/command sequence, there is no concealment or recovery for audio
28 viable recovery strategy.
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-node | 198 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.
|
| /Documentation/scsi/ |
| D | scsi_eh.rst | 179 performs during recovery. This will be discussed in [2-2].
181 Once recovery is complete, SCSI EH resumes normal operation by
209 To achieve these goals, EH performs recovery actions with increasing
227 During recovery, the following rules are followed
229 - Recovery actions are performed on failed scmds on the to do list,
230 eh_work_q. If a recovery action succeeds for a scmd, recovered
233 Note that single recovery action on a scmd can recover multiple
240 - EH reuses failed scmds to issue commands for recovery. For
335 causes higher-severity recovery to be taken for the scmd.
368 states, no further recovery action is needed.
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | ti,tsc2005.yaml | 42 ti,esd-recovery-timeout-ms:
99 ti,esd-recovery-timeout-ms = <8000>;
126 ti,esd-recovery-timeout-ms = <8000>;
|
| /Documentation/mm/ |
| D | hwpoison.rst | 9 (``MCA recovery``). This requires the OS to declare a page "poisoned",
54 Failure recovery modes
57 There are two (actually three) modes memory failure recovery can be in:
60 All memory failures cause a panic. Do not attempt recovery.
|
| /Documentation/arch/powerpc/ |
| D | eeh-pci-error-recovery.rst | 2 PCI Bus EEH Error Recovery
57 Detection and Recovery
78 Detection and recovery are performed with the aid of ppc64
92 pending work) and start recovery of the card. Recovery normally
115 At this time, a generic EEH recovery mechanism has been implemented,
117 EEH recovery. This generic mechanism piggy-backs on the PCI hotplug
162 To assist in the recovery of the device, eeh.c exports the
299 There are several issues with the current EEH software recovery design,
|
| D | index.rst | 20 eeh-pci-error-recovery
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 238 written out either when they are full, or when the recovery journal
239 requests they do so in order to allow the main recovery journal (see below)
241 recovery journal can regularly free up space, and also to amortize the cost
257 how full it is. During recovery, each physical zone will attempt to recover
299 *The Recovery Journal*
301 The recovery journal is used to amortize updates across the block map and
310 that are required for a data_vio. The recovery journal issues a flush
313 writes are all issued with the FUA bit set to ensure the recovery journal
544 10. The data_vio makes an entry in the recovery journal containing the
547 recovery journal lock. The data_vio will wait in the journal until all
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 64 - Recovery button was pressed when x86 firmware booted.
67 - Recovery button was pressed when EC firmware booted. (required if EC EEPROM is
120 (bootstrap + recovery ) portion of the main processor firmware.
163 - 0 - Read-only (recovery) firmware
172 - 0 - Recovery
228 - 0x00000001 - Recovery button
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 21 contents. PPL recovery is also performed when starting an array after an
36 silent data corruption. If a dirty disk of a stripe is lost, no PPL recovery is
|
123456