| /linux-4.4.14/arch/cris/arch-v10/lib/ |
| D | csumcpfruser.S | 42 ;; Here from a failing single byte.
45 ;; Signal in *errptr that we had a failing access.
|
| D | checksumcopy.S | 40 1: ;; A failing userspace access will have this as PC.
103 2: ;; A failing userspace access will have this as PC.
122 3: ;; A failing userspace access will have this as PC.
|
| /linux-4.4.14/arch/cris/arch-v32/lib/ |
| D | checksumcopy.S | 30 1: ;; A failing userspace access (the read) will have this as PC.
71 2: ;; A failing userspace access for the read below will have this as PC.
87 3: ;; A failing userspace access for the read below will have this as PC.
|
| D | csumcpfruser.S | 42 ;; Here from a failing single byte.
45 ;; Signal in *errptr that we had a failing access.
|
| /linux-4.4.14/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-4.4.14/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
|
| /linux-4.4.14/drivers/base/ |
| D | devcoredump.c | 208 static int devcd_match_failing(struct device *dev, const void *failing) in devcd_match_failing() argument
212 return devcd->failing_dev == failing; in devcd_match_failing()
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-flakey.txt | 6 failing devices for testing purposes.
|
| /linux-4.4.14/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
202 you may be able to search for failing drivers by following the procedure
203 analogous to the one described in section 1. If you find some failing drivers,
|
| D | runtime_pm.txt | 239 this flag is cleared; this is the error code returned by the failing
|
| D | pci.txt | 525 only is necessary in the error path during a failing suspend). Next, resume
|
| /linux-4.4.14/Documentation/laptops/ |
| D | toshiba_haps.txt | 44 any "protection" as well as failing during the evaluation of the _STA method
|
| /linux-4.4.14/Documentation/usb/ |
| D | callbacks.txt | 88 to deal with failing IO even prior to the callback.
|
| /linux-4.4.14/Documentation/vm/ |
| D | ksm.txt | 30 more memory than is available - possibly failing with EAGAIN, but more
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-kmem.txt | 104 high-order allocations will start failing at some time in the future. One
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices-edac | 63 to indicate which slot the failing memory is in. This count
|
| /linux-4.4.14/fs/ubifs/ |
| D | debug.c | 2574 int err, failing; in dbg_leb_write() local
2579 failing = power_cut_emulated(c, lnum, 1); in dbg_leb_write()
2580 if (failing) { in dbg_leb_write()
2588 if (failing) in dbg_leb_write()
|
| /linux-4.4.14/drivers/iommu/ |
| D | Kconfig | 179 thereby failing to work when IOMMU is enabled. This
|
| /linux-4.4.14/drivers/edac/ |
| D | Kconfig | 72 occurred so that a particular failing memory module can be
|
| /linux-4.4.14/Documentation/ia64/ |
| D | mca.txt | 83 trace of the failing handler's "task".
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_eh.txt | 344 immediate failing; thus, if a sdev is in one of the two
|
| D | ChangeLog.megaraid_sas | 468 5. Performing diskdump while running IO in RHEL 4 was failing. Fixed.
|
| D | ChangeLog.lpfc | 41 * Clear host_scribble in the scsi_cmnd structure when failing in
477 midlayer to mark report luns as failing even though it
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 50 periods, failing to omit scheduling-clock interrupts will result in
|
| /linux-4.4.14/Documentation/RCU/ |
| D | checklist.txt | 238 cases where grace periods are delayed, as failing to do so can
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 129 already have "noticed" the error because of a failing I/O, but this
|
| /linux-4.4.14/Documentation/networking/ |
| D | ppp_generic.txt | 376 out why a PPP connection is failing.
|
| D | bonding.txt | 2712 If link monitoring is enabled, then the failing device will be
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 189 cache in the parent's list will be chosen, or failing that, the first
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | README.DAC960 | 242 rather than accepting the default 2GB BIOS Geometry (128/32); failing to so do
|
| /linux-4.4.14/Documentation/security/ |
| D | Smack.txt | 306 often sited as failing to address general needs.
|
| D | keys.txt | 1229 after all allocations and other potentially failing function calls are
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 652 on task attaching. In this failing case, those tasks will stay
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 462 from failing on read and write if we use mandatory brlock style.
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 12 subsequently opening the file and then failing to write to it for
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 3288 # _mem_write() "callout" routines that may return a failing result. #
|
| D | fpsp.S | 3289 # _mem_write() "callout" routines that may return a failing result. #
|