Searched full:failures (Results 1 – 25 of 91) sorted by relevance
1234
| /Documentation/mm/ |
| D | hwpoison.rst | 29 users, because memory failures could happen anytime and anywhere,
51 memory failures too. The expectation is that most applications
60 All memory failures cause a panic. Do not attempt recovery.
121 injected failures, not for real memory failures. Once any hardware
128 Only handle memory failures to pages associated with the file
|
| /Documentation/fault-injection/ |
| D | fault-injection.rst | 13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
17 injects page allocation failures. (alloc_pages(), get_free_pages(), ...)
21 injects failures in user memory access functions. (copy_from_user(), get_user(), ...)
29 injects kernel RPC client and server failures.
85 specifies the interval between failures, for calls to
93 specifies how many times failures may happen at most. A value of -1
116 Any positive value limits failures to only processes indicated by
141 default is 'Y', setting it to 'N' will also inject failures into
147 default is 'N', setting it to 'Y' will only inject failures when
157 default is 'Y', setting it to 'N' will also inject failures
[all …]
|
| D | provoke-crashes.rst | 46 You can also induce failures by mounting debugfs and writing the type to
|
| D | notifier-error-inject.rst | 6 notifier call chain failures which is rarely executed. There are kernel
|
| /Documentation/netlink/specs/ |
| D | binder.yaml | 71 binder transaction failures. The generated report provides the full
73 programs to monitor these events and react to the failures as needed.
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-incfs | 59 failures.
65 timing out or hash failures.
|
| D | sysfs-class-mtd | 193 The number of failures reported by this device's ECC. Typically,
194 these failures are associated with failed read operations.
|
| /Documentation/filesystems/ |
| D | incfs.rst | 68 Returns number of reads that failed because of hash verification failures.
72 hash failures.
|
| D | ceph.rst | 16 * Fast recovery from node failures
39 and can tolerate arbitrary (well, non-Byzantine) node failures. The
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 113 On some architectures allocation failures are reported with error messages
115 drivers which handle failures (eg, retry later) have no problems with them,
120 where allocation failures are not a problem, and shouldn't bother the logs.
|
| D | memory-allocation.rst | 49 to provide a suitable fallback to cope with such failures where
115 that behavior so failures have to be checked properly by callers
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-queue-length.rst | 23 <fail-count>: The number of path failures.
|
| D | dm-dust.rst | 5 locations, and the ability to enable the emulation of the failures
108 Enabling block read failures
114 kernel: device-mapper: dust: enabling read failures on bad sectors
|
| D | dm-service-time.rst | 38 The number of path failures.
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 191 That test can be used to check if failures to resume from hibernation are
194 unreliable, the platform firmware may be responsible for the failures.
199 kernel address space randomization, it also can be used to check if failures
258 failures:
|
| D | freezing-of-tasks.rst | 224 VI. Are there any precautions to be taken to prevent freezing failures?
238 failures, because if the suspend/hibernate code successfully acquired the
249 mutex_[un]lock(&system_transition_mutex). That would prevent freezing failures.
|
| /Documentation/admin-guide/mm/ |
| D | zswap.rst | 127 Some users cannot tolerate the swapping that comes with zswap store failures
133 Note that if the store failures are recurring (for e.g if the pages are
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra234-cbb.yaml | 36 that initiator. The value returned on read failures is '0xFFFFFFFF'
|
| /Documentation/virt/coco/ |
| D | tdx-guest.rst | 30 common failures.
|
| /Documentation/RCU/ |
| D | torture.rst | 154 were no RCU failures, CPU-hotplug problems were detected.
232 for tracking down rare boot-time failures.
241 If a run contains failures, the number of buildtime and runtime failures
|
| /Documentation/gpu/ |
| D | automated_testing.rst | 61 Lists the known failures for a given driver on a specific hardware revision.
127 and then the expected results if there are any known failures.
|
| /Documentation/arch/powerpc/ |
| D | dawr-power9.rst | 101 Any errors/failures/skips mean something is wrong.
|
| /Documentation/process/ |
| D | submit-checklist.rst | 127 failures. See ``Documentation/fault-injection/``.
|
| /Documentation/hwmon/ |
| D | ltc4282.rst | 113 The chip also has a fault log register where failures can be logged. Hence,
|
| /Documentation/mm/damon/ |
| D | maintainer-profile.rst | 39 - Run and ensure no new failures for DAMON `selftests
|
1234