Home
last modified time | relevance | path

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

12

/linux-5.19.10/crypto/
Djitterentropy.c207 static void jent_rct_insert(struct rand_data *ec, int stuck) in jent_rct_insert() argument
216 if (stuck) { in jent_rct_insert()
393 int stuck) in jent_lfsr_time() argument
445 if (!stuck) in jent_lfsr_time()
531 int stuck; in jent_measure_jitter() local
545 stuck = jent_stuck(ec, current_delta); in jent_measure_jitter()
548 jent_lfsr_time(ec, current_delta, 0, stuck); in jent_measure_jitter()
550 return stuck; in jent_measure_jitter()
757 int stuck; in jent_entropy_init() local
777 stuck = jent_stuck(&ec, delta); in jent_entropy_init()
[all …]
/linux-5.19.10/arch/sparc/kernel/
Dsmp_64.c399 int stuck, tmp; in spitfire_xcall_helper() local
437 stuck = 100000; in spitfire_xcall_helper()
447 stuck -= 1; in spitfire_xcall_helper()
448 if (stuck == 0) in spitfire_xcall_helper()
453 if (stuck == 0) { in spitfire_xcall_helper()
553 long stuck; in cheetah_xcall_deliver() local
555 stuck = 100000 * nack_busy_id; in cheetah_xcall_deliver()
578 if (!--stuck) in cheetah_xcall_deliver()
/linux-5.19.10/fs/xfs/
Dxfs_trans_ail.c427 int stuck = 0; in xfsaild_push() local
516 stuck++; in xfsaild_push()
523 stuck++; in xfsaild_push()
545 if (stuck > 100) in xfsaild_push()
569 } else if (((stuck + flushing) * 100) / count > 90) { in xfsaild_push()
/linux-5.19.10/Documentation/hwmon/
Dasus_wmi_sensors.rst70 fans stopping, fans getting stuck at max speed, or temperature readouts
71 getting stuck. This is not an issue with the driver, but the BIOS. The Prime
Dasb100.rst67 be read-only or otherwise stuck at 0x00.
/linux-5.19.10/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-5.19.10/Documentation/networking/
Dipddp.rst69 Encapsulation has been used to allow a Linux box stuck on a LocalTalk
70 network to use IP. It should work equally well if you are stuck on an
Dnet_dim.rst69 done in order to avoid getting stuck in a "deep sleep" scenario. Once a
/linux-5.19.10/Documentation/networking/devlink/
Dmlx4.rst51 In case a firmware command times out, firmware getting stuck, or a non zero
/linux-5.19.10/drivers/md/bcache/
DKconfig29 operations that get stuck.
/linux-5.19.10/drivers/net/appletalk/
DKconfig78 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
100 is stuck on an AppleTalk network (which hopefully contains a
/linux-5.19.10/Documentation/devicetree/bindings/input/
Dqcom,pm8xxx-keypad.txt21 and the second interrupt specifies the key stuck interrupt.
/linux-5.19.10/Documentation/ABI/testing/
Dsysfs-class-bdi55 mount that is prone to get stuck, or a FUSE mount which cannot
/linux-5.19.10/Documentation/devicetree/bindings/display/
Dbrcm,bcm2711-hdmi.yaml60 - description: CEC stuck at low interrupt
/linux-5.19.10/arch/powerpc/platforms/powermac/
Dsmp.c376 goto stuck; in smp_psurge_kick_cpu()
390 stuck: in smp_psurge_kick_cpu()
/linux-5.19.10/Documentation/i2c/
Dgpio-fault-injection.rst48 there are I2C client devices which detect a stuck SDA on their side and release
50 device deglitching and monitoring the I2C bus. It could also detect a stuck SDA
/linux-5.19.10/Documentation/process/
Dbotching-up-ioctls.rst113 now we're stuck forever with some arcane semantics in both the kernel and
116 * If you can't make a given codepath restartable make a stuck task at least
222 be stuck with a given ioctl essentially forever. You can try to deprecate
/linux-5.19.10/arch/arm/boot/dts/
Dimx6qdl-sr-som.dtsi60 * some rare issues where the PHY gets stuck in an inconsistent and
/linux-5.19.10/tools/virtio/virtio-trace/
DREADME108 If a host does not open these, trace data get stuck in buffers of virtio. Then,
/linux-5.19.10/Documentation/arm64/
Dasymmetric-32bit.rst29 altogether, so if you're stuck in the unenviable position of needing to
/linux-5.19.10/Documentation/networking/device_drivers/ethernet/3com/
Dvortex.rst233 decides that the transmitter has become stuck and needs to be reset.
259 get stuck on the 10base2 port and a driver reload was necessary to
/linux-5.19.10/Documentation/input/devices/
Datarikbd.rst194 major controller faults (ROM checksum and RAM test) and such things as stuck
195 keys. Any keys down at power-up are presumed to be stuck, and their BREAK
236 ikbd will then scan the key matrix for any stuck (closed) keys. Any keys found
/linux-5.19.10/drivers/usb/gadget/udc/
Dnet2280.c2606 int stuck = 0; in handle_ep_small() local
2646 req->td_dma && stuck++ > 5) { in handle_ep_small()
2652 ep->ep.name, stuck, in handle_ep_small()
2657 stuck = 0; in handle_ep_small()
2661 stuck = 0; in handle_ep_small()
/linux-5.19.10/Documentation/livepatch/
Dlivepatch.rst135 are stuck in the initial patch state.
158 transition gets stuck for a long time because of a blocking task. Administrator
/linux-5.19.10/Documentation/admin-guide/nfs/
Dnfs-rdma.rst28 If you get stuck, you can ask questions on the

12