Searched full:fail (Results 1 – 25 of 391) sorted by relevance
12345678910>>...16
| /Documentation/fault-injection/ |
| D | fault-injection.rst | 34 /sys/block/<device>/make-it-fail or 35 /sys/block/<device>/<partition>/make-it-fail. (submit_bio_noacct()) 73 - /sys/kernel/debug/fail*/probability: 81 /sys/kernel/debug/fail*/interval for such testcases. 83 - /sys/kernel/debug/fail*/interval: 91 - /sys/kernel/debug/fail*/times: 96 - /sys/kernel/debug/fail*/space: 102 - /sys/kernel/debug/fail*/verbose 111 - /sys/kernel/debug/fail*/task-filter: 117 /proc/<pid>/make-it-fail==1. [all …]
|
| /Documentation/litmus-tests/ |
| D | README | 24 cmpxchg-fail-ordered-1.litmus 28 cmpxchg-fail-ordered-2.litmus 32 cmpxchg-fail-unordered-1.litmus 36 cmpxchg-fail-unordered-2.litmus
|
| /Documentation/ABI/testing/ |
| 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 | 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 | 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>:
|
| /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. Users of this flag need 114 allocation requests are basically no-fail but there is no guarantee of 116 (e.g. OOM killer victim is allowed to fail currently). 119 and all allocation requests fail early rather than cause disruptive 125 will fail if the reclaim cannot make any progress. The OOM killer
|
| D | cpu_hotplug.rst | 192 The startup callbacks are allowed to fail. If a callback fails, the CPU 196 The teardown callbacks in this section are not allowed to fail. 209 The callbacks in this section are not allowed to fail. 227 The callbacks are allowed to fail. When a callback fails the hotplug 284 [CPUHP_AP_ONLINE + N]->startup() -> fail 305 [CPUHP_ONLINE - N]->teardown() -> fail 312 example of a recursive fail due to a failed offline operation: :: 317 [CPUHP_ONLINE - N]->teardown() -> fail 319 [CPUHP_ONLINE - (N - 2)]->startup() -> fail 325 [CPUHP_ONLINE - N]->teardown() -> fail [all …]
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | mdss-common.yaml | 59 - description: Phandle to apps_smmu node with SID mask for Hard-Fail port0 60 - description: Phandle to apps_smmu node with SID mask for Hard-Fail port1
|
| /Documentation/sound/cards/ |
| D | via82xx-mixer.rst | 6 Setting it to ``Input2`` on such boards will cause recording to hang, or fail
|
| /Documentation/litmus-tests/atomic/ |
| D | cmpxchg-fail-ordered-2.litmus | 1 C cmpxchg-fail-ordered-2
|
| D | cmpxchg-fail-unordered-2.litmus | 1 C cmpxchg-fail-unordered-2
|
| D | cmpxchg-fail-ordered-1.litmus | 1 C cmpxchg-fail-ordered-1
|
| D | cmpxchg-fail-unordered-1.litmus | 1 C cmpxchg-fail-unordered-1
|
| /Documentation/dev-tools/ |
| D | ktap.rst | 102 - "XFAIL", which indicates that a test is expected to fail. This is similar 191 result. If one of the subtests fail, for example, the parent test should also 192 fail. 270 # test_2: FAIL 291 - "test_2", which outputs the diagnostic line "test_2: FAIL", and fails. 296 rules for "bubbling up" test results: a test fails if any of its subtests fail.
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | qcom,pm8916-lbc.yaml | 69 in which case, setting this will harmlessly fail. 77 bootloader, in which case setting this will harmlessly 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/scsi/scsi_transport_srp/ |
| D | rport_state_diagram.dot | 11 failfast [ label = "fail I/O\nfast" ];
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 56 * if the parents don't have a common ancestor, fail the operation. 61 target is not a descendent of source; fail the operation otherwise. 96 and fail the lookup if it is. Then we try to lock the filesystem and the 97 current parent of the alias. If either trylock fails, we fail the lookup. 247 in between (all of those would fail with -ENOTEMPTY, had they ever gotten
|
12345678910>>...16