Searched full:fail (Results 1 – 25 of 312) sorted by relevance
12345678910>>...13
| /Documentation/fault-injection/ |
| D | fault-injection.rst | 30 /sys/block/<device>/make-it-fail or
31 /sys/block/<device>/<partition>/make-it-fail. (submit_bio_noacct())
61 - /sys/kernel/debug/fail*/probability:
69 /sys/kernel/debug/fail*/interval for such testcases.
71 - /sys/kernel/debug/fail*/interval:
79 - /sys/kernel/debug/fail*/times:
84 - /sys/kernel/debug/fail*/space:
90 - /sys/kernel/debug/fail*/verbose
99 - /sys/kernel/debug/fail*/task-filter:
105 /proc/<pid>/make-it-fail==1.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-rnbd | 8 When "normal" is used, the operation will fail with EBUSY if any process
10 when device is in use. All I/Os that are in progress will fail.
24 returns "closed" and all I/O requests submitted to it will fail with -EIO.
|
| D | sysfs-class-rc | 53 the filter will be ignored. Otherwise the write will fail with
70 the filter will be ignored. Otherwise the write will fail with
116 Otherwise the write will fail with an error.
135 Otherwise the write will fail with an error.
|
| D | configfs-stp-policy | 16 stm device, mkdir will fail with ENODEV; if that device already
17 has a policy assigned to it, mkdir will fail with EBUSY.
|
| D | configfs-acpi | 25 subsequent writes to this attribute will fail.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-queue-length.rst | 18 Status for each path: <status> <fail-count> <in-flight>
23 <fail-count>: The number of path failures.
|
| D | dm-service-time.rst | 34 <status> <fail-count> <in-flight-size> <relative_throughput>
37 <fail-count>:
|
| D | dm-dust.rst | 15 in the "bad block list" will fail with EIO ("Input/output error").
111 To enable the "fail read on bad block" behavior, send the "enable" message::
119 With the device in "fail read on bad block" mode, attempting to read a
285 scsi_debug has a "medium error" mode that can fail reads on one
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-sysfs-nodes.rst | 66 ignored. Otherwise the write will fail with an error.
82 will be ignored. Otherwise the write will fail with an error.
125 to RAM or power off. Otherwise the write will fail with an error.
142 to RAM or power off. Otherwise the write will fail with an error.
|
| /Documentation/PCI/endpoint/ |
| D | pci-test-function.rst | 60 Bit 1 read fail
62 Bit 3 write fail
64 Bit 5 copy fail
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 48 ``GFP_NOWAIT`` allocation is likely to fail. Allocations which
113 allocation requests are basically no-fail but there is no guarantee of
115 (e.g. OOM killer victim is allowed to fail currently).
118 and all allocation requests fail early rather than cause disruptive
124 will fail if the reclaim cannot make any progress. The OOM killer
|
| /Documentation/sound/cards/ |
| D | via82xx-mixer.rst | 6 Setting it to ``Input2`` on such boards will cause recording to hang, or fail
|
| /Documentation/hwmon/ |
| D | ibmpowernv.rst | 36 fanX_fault - 0: No fail condition
52 inX_fault - 0: No fail condition.
|
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtmv20-regulator.yaml | 15 (Enable/Fail), Enable pin to turn chip on, and Fail pin as fault indication.
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-mmap.rst | 33 multiple of the pagesize and mmap will fail when the specified
56 :c:func:`mmap()` will fail. If ``MAP_FIXED`` is specified,
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 53 fail with -ENOTEMPTY
55 fail with -ELOOP
136 we had acquired filesystem lock and rename() would fail with -ELOOP in that
|
| /Documentation/powerpc/ |
| D | dawr-power9.rst | 49 host. The watchpoint will fail and GDB will fall back to software
86 dawr_enable_dangerous file will fail if the hypervisor doesn't support
|
| /Documentation/scsi/scsi_transport_srp/ |
| D | rport_state_diagram.dot | 11 failfast [ label = "fail I/O\nfast" ];
|
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 5 # 80 chars should be enough, but don't fail if a line is longer
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 104 the "platform" test will fail as well and so on. Thus, as a rule of thumb, you
130 It is also possible that the "devices" test will still fail after you have
234 you to identify drivers that fail to suspend or resume their devices. They
251 fail: 5
266 Field success means the success number of suspend to RAM, and field fail means
|
| /Documentation/crypto/ |
| D | api-intro.rst | 65 fail();
71 fail();
77 fail();
|
| /Documentation/arm/ |
| D | swp_emulation.rst | 27 the STREX operation will always fail.
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-mmap.rst | 31 multiple of the pagesize and mmap will fail when the specified
71 :c:func:`mmap()` will fail. If ``MAP_FIXED`` is specified,
|
| /Documentation/security/keys/ |
| D | request-key.rst | 138 the key while it exists to fail with error ENOKEY if negated or the specified
199 Only if all these fail does the whole thing fail with the highest priority
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 23 /value ... always readable, writes fail for input GPIOs
|
12345678910>>...13