Searched refs:failing (Results 1 – 25 of 44) sorted by relevance
12
51 a failing value to the 68060SP, the package ignores53 as if it never received a failing value.59 requested by the package should return a failing value71 Upon receiving a non-zero (failing) return value from
22 layer error has been observed before failing I/O. Zero means23 failing I/O immediately. Setting this attribute to "off" will
128 filtering or failing outbound partition or IP version check.132 inbound raw filtering or failing inbound partition or IP version
18 failing over to the paravirtual datapath when the VF is unplugged.
25 direct attached VF by failing over to the paravirtual datapath when the VF
192 static int devcd_match_failing(struct device *dev, const void *failing) in devcd_match_failing() argument196 return devcd->failing_dev == failing; in devcd_match_failing()
7 failing devices for testing purposes.
9 the user can send a message to the target to start failing read
111 dmesg obtained after the failing test). Failure at this level usually means126 Once you have found the failing driver (there can be more than just one of240 you may be able to search for failing drivers by following the procedure241 analogous to the one described in section 1. If you find some failing drivers,
48 any "protection" as well as failing during the evaluation of the _STA method
181 bugs, or failing to map some of the exit code.190 as mount(8) failing to mount the rootfs. These have
36 failing to work with the default driver settings.
63 to indicate which slot the failing memory is in. This count
107 to deal with failing IO even prior to the callback.
116 high-order allocations will start failing at some time in the future. One
2571 int err, failing; in dbg_leb_write() local2576 failing = power_cut_emulated(c, lnum, 1); in dbg_leb_write()2577 if (failing) { in dbg_leb_write()2585 if (failing) in dbg_leb_write()
49 may suddenly require more memory than is available - possibly failing
69 output captured from the failing test will be printed immediately following
86 trace of the failing handler's "task".
448 migration of VMs with direct attached VFs by failing over to the
241 thereby failing to work when IOMMU is enabled. This
53 periods, failing to omit scheduling-clock interrupts will result in
333 immediate failing; thus, if a sdev is in one of the two
527 a VM with direct attached VF by failing over to the paravirtual
570 failng||failing
