Home
last modified time | relevance | path

Searched refs:stuck (Results 1 – 28 of 28) sorted by relevance

/linux-4.1.27/fs/xfs/
Dxfs_trans_ail.c338 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.1.27/arch/sparc/kernel/
Dsmp_64.c393 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.1.27/drivers/md/bcache/
DKconfig26 operations that get stuck.
/linux-4.1.27/drivers/infiniband/hw/qib/
Dqib_qsfp.c52 int stuck = 0; in qsfp_read() local
92 stuck = 1; in qsfp_read()
135 if (stuck) in qsfp_read()
/linux-4.1.27/Documentation/networking/
Dipddp.txt64 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
Dvortex.txt222 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.1.27/drivers/net/appletalk/
DKconfig85 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.1.27/Documentation/video4linux/bttv/
DREADME.WINVIEW6 GPIO lines in order to give some volume control. They have also stuck an
DREADME.freeze32 state is stuck.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-bdi49 mount that is prone to get stuck, or a FUSE mount which cannot
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dqcom,pm8xxx-keypad.txt21 and the second interrupt specifies the key stuck interrupt.
/linux-4.1.27/Documentation/hwmon/
Dasb10065 be read-only or otherwise stuck at 0x00.
Dw83781d288 and 4 is ignored/stuck, on AMD boards sensor 4 is the CPU and sensor 2 is
/linux-4.1.27/arch/powerpc/platforms/powermac/
Dsmp.c382 goto stuck; in smp_psurge_kick_cpu()
396 stuck: in smp_psurge_kick_cpu()
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt107 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.1.27/arch/cris/arch-v32/mm/
Dmmu.S71 ; doesn't recognize it and we get stuck in a loop of refill exceptions.
/linux-4.1.27/tools/virtio/virtio-trace/
DREADME108 If a host does not open these, trace data get stuck in buffers of virtio. Then,
/linux-4.1.27/Documentation/input/
Datarikbd.txt169 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.1.27/Documentation/filesystems/nfs/
Dnfs-rdma.txt35 If you get stuck, you can ask questions on the
/linux-4.1.27/drivers/net/ethernet/myricom/myri10ge/
Dmyri10ge.c188 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.1.27/Documentation/
Dsysrq.txt177 * Sometimes SysRq seems to get 'stuck' after using it, what can I do?
/linux-4.1.27/drivers/gpu/drm/i915/
Di915_irq.c2860 bool stuck[I915_NUM_RINGS] = { 0 }; in i915_hangcheck_elapsed() local
2929 stuck[i] = true; in i915_hangcheck_elapsed()
2953 stuck[i] ? "stuck" : "no progress", in i915_hangcheck_elapsed()
/linux-4.1.27/Documentation/sound/oss/
DIntroduction225 If you get really stuck or have a card that the kernel modules
/linux-4.1.27/Documentation/scsi/
Dtmscsim.txt386 * In some situations, the driver will get stuck in an abort loop. This is a
DChangeLog.sym53c8xx593 better to fail when we are stuck.
/linux-4.1.27/lib/
DKconfig.debug757 which are bugs that cause the task to be stuck in
787 which are bugs that cause the kernel to leave a task stuck
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES310 Timeout stuck requests better (where server has never responded or sent corrupt
/linux-4.1.27/Documentation/s390/
DDebugging390.txt2084 (e.g. the txbusy field of the network device being stuck on )