/linux-4.4.14/crypto/ |
D | jitterentropy.c | 74 unsigned int stuck:1; /* Time measurement stuck */ member 328 ec->stuck = 1; in jent_stuck() 491 if (ec->stuck) { in jent_gen_entropy() 503 ec->stuck = 0; in jent_gen_entropy()
|
/linux-4.4.14/fs/xfs/ |
D | xfs_trans_ail.c | 338 int stuck = 0; in xfsaild_push() local 417 stuck++; in xfsaild_push() 424 stuck++; in xfsaild_push() 446 if (stuck > 100) in xfsaild_push() 469 } else if (((stuck + flushing) * 100) / count > 90) { in xfsaild_push()
|
/linux-4.4.14/arch/sparc/kernel/ |
D | smp_64.c | 393 int stuck, tmp; in spitfire_xcall_helper() local 431 stuck = 100000; in spitfire_xcall_helper() 441 stuck -= 1; in spitfire_xcall_helper() 442 if (stuck == 0) in spitfire_xcall_helper() 447 if (stuck == 0) { in spitfire_xcall_helper() 547 long stuck; in cheetah_xcall_deliver() local 549 stuck = 100000 * nack_busy_id; in cheetah_xcall_deliver() 572 if (!--stuck) in cheetah_xcall_deliver()
|
/linux-4.4.14/drivers/md/bcache/ |
D | Kconfig | 26 operations that get stuck.
|
/linux-4.4.14/drivers/staging/rdma/hfi1/ |
D | qsfp.c | 125 int stuck = 0; in __i2c_read() local 134 stuck = 1; in __i2c_read() 159 if (stuck) in __i2c_read()
|
/linux-4.4.14/drivers/infiniband/hw/qib/ |
D | qib_qsfp.c | 52 int stuck = 0; in qsfp_read() local 92 stuck = 1; in qsfp_read() 135 if (stuck) in qsfp_read()
|
/linux-4.4.14/Documentation/networking/ |
D | ipddp.txt | 64 Encapsulation has been used to allow a Linux box stuck on a LocalTalk 65 network to use IP. It should work equally well if you are stuck on an
|
D | vortex.txt | 222 decides that the transmitter has become stuck and needs to be reset. 248 get stuck on the 10base2 port and a driver reload was necessary to
|
/linux-4.4.14/drivers/net/appletalk/ |
D | Kconfig | 85 box is stuck on an AppleTalk only network) or decapsulate (e.g. if 107 is stuck on an AppleTalk network (which hopefully contains a
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-class-bdi | 49 mount that is prone to get stuck, or a FUSE mount which cannot
|
/linux-4.4.14/Documentation/video4linux/bttv/ |
D | README.WINVIEW | 6 GPIO lines in order to give some volume control. They have also stuck an
|
D | README.freeze | 32 state is stuck.
|
/linux-4.4.14/Documentation/devicetree/bindings/input/ |
D | qcom,pm8xxx-keypad.txt | 21 and the second interrupt specifies the key stuck interrupt.
|
/linux-4.4.14/Documentation/hwmon/ |
D | asb100 | 65 be read-only or otherwise stuck at 0x00.
|
D | w83781d | 288 and 4 is ignored/stuck, on AMD boards sensor 4 is the CPU and sensor 2 is
|
/linux-4.4.14/arch/powerpc/platforms/powermac/ |
D | smp.c | 382 goto stuck; in smp_psurge_kick_cpu() 396 stuck: in smp_psurge_kick_cpu()
|
/linux-4.4.14/Documentation/ioctl/ |
D | botching-up-ioctls.txt | 107 now we're stuck forever with some arcane semantics in both the kernel and 110 * If you can't make a given codepath restartable make a stuck task at least 216 be stuck with a given ioctl essentially forever. You can try to deprecate
|
/linux-4.4.14/tools/virtio/virtio-trace/ |
D | README | 108 If a host does not open these, trace data get stuck in buffers of virtio. Then,
|
/linux-4.4.14/arch/cris/arch-v32/mm/ |
D | mmu.S | 71 ; doesn't recognize it and we get stuck in a loop of refill exceptions.
|
/linux-4.4.14/Documentation/input/ |
D | atarikbd.txt | 169 major controller faults (ROM checksum and RAM test) and such things as stuck 170 keys. Any keys down at power-up are presumed to be stuck, and their BREAK 207 ikbd will then scan the key matrix for any stuck (closed) keys. Any keys found
|
/linux-4.4.14/Documentation/filesystems/nfs/ |
D | nfs-rdma.txt | 35 If you get stuck, you can ask questions on the
|
/linux-4.4.14/drivers/net/ethernet/myricom/myri10ge/ |
D | myri10ge.c | 188 int stuck; member 3590 ss->stuck = 1; in myri10ge_check_slice() 3664 if (ss->stuck) { in myri10ge_watchdog() 3668 ss->stuck = 0; in myri10ge_watchdog()
|
/linux-4.4.14/Documentation/ |
D | sysrq.txt | 179 * Sometimes SysRq seems to get 'stuck' after using it, what can I do?
|
/linux-4.4.14/drivers/gpu/drm/i915/ |
D | i915_irq.c | 2960 bool stuck[I915_NUM_RINGS] = { 0 }; in i915_hangcheck_elapsed() local 3029 stuck[i] = true; in i915_hangcheck_elapsed() 3053 stuck[i] ? "stuck" : "no progress", in i915_hangcheck_elapsed()
|
/linux-4.4.14/Documentation/sound/oss/ |
D | Introduction | 225 If you get really stuck or have a card that the kernel modules
|
/linux-4.4.14/Documentation/scsi/ |
D | tmscsim.txt | 386 * In some situations, the driver will get stuck in an abort loop. This is a
|
D | ChangeLog.sym53c8xx | 593 better to fail when we are stuck.
|
/linux-4.4.14/lib/ |
D | Kconfig.debug | 767 which are bugs that cause the task to be stuck in 797 which are bugs that cause the kernel to leave a task stuck
|
/linux-4.4.14/Documentation/filesystems/cifs/ |
D | CHANGES | 310 Timeout stuck requests better (where server has never responded or sent corrupt
|
/linux-4.4.14/Documentation/s390/ |
D | Debugging390.txt | 2084 (e.g. the txbusy field of the network device being stuck on )
|