Searched refs:failing (Results 1 – 25 of 44) sorted by relevance
12
| /Linux-v4.19/arch/m68k/ifpsp060/ |
| D | CHANGES | 51 a failing value to the 68060SP, the package ignores
53 as if it never received a failing value.
59 requested by the package should return a failing value
71 Upon receiving a non-zero (failing) return value from
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 22 layer error has been observed before failing I/O. Zero means
23 failing I/O immediately. Setting this attribute to "off" will
|
| D | sysfs-class-infiniband | 128 filtering or failing outbound partition or IP version check.
132 inbound raw filtering or failing inbound partition or IP version
|
| /Linux-v4.19/Documentation/networking/ |
| D | failover.rst | 18 failing over to the paravirtual datapath when the VF is unplugged.
|
| D | net_failover.rst | 25 direct attached VF by failing over to the paravirtual datapath when the VF
|
| /Linux-v4.19/drivers/base/ |
| D | devcoredump.c | 201 static int devcd_match_failing(struct device *dev, const void *failing) in devcd_match_failing() argument
205 return devcd->failing_dev == failing; in devcd_match_failing()
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-flakey.txt | 6 failing devices for testing purposes.
|
| /Linux-v4.19/Documentation/power/ |
| D | basic-pm-debugging.txt | 103 dmesg obtained after the failing test). Failure at this level usually means
117 Once you have found the failing driver (there can be more than just one of
227 you may be able to search for failing drivers by following the procedure
228 analogous to the one described in section 1. If you find some failing drivers,
|
| /Linux-v4.19/Documentation/laptops/ |
| D | toshiba_haps.txt | 44 any "protection" as well as failing during the evaluation of the _STA method
|
| /Linux-v4.19/Documentation/x86/ |
| D | pti.txt | 172 bugs, or failing to map some of the exit code.
181 as mount(8) failing to mount the rootfs. These have
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | callbacks.rst | 107 to deal with failing IO even prior to the callback.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-net-cdc_ncm | 36 failing to work with the default driver settings.
|
| D | sysfs-devices-edac | 63 to indicate which slot the failing memory is in. This count
|
| /Linux-v4.19/Documentation/trace/ |
| D | events-kmem.rst | 116 high-order allocations will start failing at some time in the future. One
|
| /Linux-v4.19/fs/ubifs/ |
| D | debug.c | 2578 int err, failing; in dbg_leb_write() local
2583 failing = power_cut_emulated(c, lnum, 1); in dbg_leb_write()
2584 if (failing) { in dbg_leb_write()
2592 if (failing) in dbg_leb_write()
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | ksm.rst | 49 may suddenly require more memory than is available - possibly failing
|
| /Linux-v4.19/tools/testing/selftests/tc-testing/ |
| D | README | 65 output captured from the failing test will be printed immediately following
|
| /Linux-v4.19/Documentation/ia64/ |
| D | mca.txt | 83 trace of the failing handler's "task".
|
| /Linux-v4.19/drivers/iommu/ |
| D | Kconfig | 224 thereby failing to work when IOMMU is enabled. This
|
| /Linux-v4.19/net/ |
| D | Kconfig | 445 migration of VMs with direct attached VFs by failing over to the
|
| /Linux-v4.19/Documentation/scsi/ |
| D | scsi_eh.txt | 333 immediate failing; thus, if a sdev is in one of the two
|
| /Linux-v4.19/Documentation/timers/ |
| D | NO_HZ.txt | 50 periods, failing to omit scheduling-clock interrupts will result in
|
| /Linux-v4.19/Documentation/livepatch/ |
| D | callbacks.txt | 419 module is later loaded, have the livepatch return a failing status code:
|
| /Linux-v4.19/scripts/ |
| D | spelling.txt | 530 failng||failing
|
| /Linux-v4.19/drivers/net/ |
| D | Kconfig | 523 a VM with direct attached VF by failing over to the paravirtual
|
12
