| /linux/crypto/ |
| H A D | jitterentropy.c | 266 static void jent_rct_insert(struct rand_data *ec, int stuck) in jent_rct_insert() argument
268 if (stuck) { in jent_rct_insert()
423 static int jent_condition_data(struct rand_data *ec, __u64 time, int stuck) in jent_condition_data() argument
439 SHA3_HASH_LOOP, stuck); in jent_condition_data()
524 int stuck; in jent_measure_jitter() local
538 stuck = jent_stuck(ec, current_delta); in jent_measure_jitter()
541 if (jent_condition_data(ec, current_delta, stuck)) in jent_measure_jitter()
542 stuck = 1; in jent_measure_jitter()
548 return stuck; in jent_measure_jitter()
|
| H A D | jitterentropy-kcapi.c | 106 unsigned int stuck) in jent_hash_time() argument
160 if (!stuck) { in jent_hash_time()
|
| /linux/fs/xfs/ |
| H A D | xfs_trans_ail.c | 475 int stuck = 0; in xfsaild_push() local
555 stuck++; in xfsaild_push()
562 stuck++; in xfsaild_push()
584 if (stuck > 100) in xfsaild_push()
612 } else if (((stuck + flushing) * 100) / count > 90) { in xfsaild_push()
|
| /linux/Documentation/hwmon/ |
| H A D | asus_wmi_sensors.rst | 70 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
|
| H A D | asb100.rst | 67 be read-only or otherwise stuck at 0x00.
|
| H A D | w83781d.rst | 332 and 4 is ignored/stuck, on AMD boards sensor 4 is the CPU and sensor 2 is
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-bdi | 70 mount that is prone to get stuck, or a FUSE mount which cannot
83 in case of an NFS mount that is prone to get stuck, or a FUSE mount
111 mount that is prone to get stuck, a FUSE mount which cannot be
|
| /linux/drivers/gpu/drm/ci/xfails/ |
| H A D | msm-apq8096-skips.txt | 26 # watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/u16:3:46]
|
| /linux/drivers/infiniband/hw/qib/ |
| H A 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/Documentation/networking/devlink/ |
| H A D | mlx4.rst | 51 In case a firmware command times out, firmware getting stuck, or a non zero
|
| /linux/fs/bcachefs/ |
| H A D | journal.c | 140 bool stuck = false; in journal_error_check_stuck() local
147 return stuck; in journal_error_check_stuck()
153 return stuck; in journal_error_check_stuck()
156 stuck = true; in journal_error_check_stuck()
165 return stuck; in journal_error_check_stuck()
183 return stuck; in journal_error_check_stuck()
|
| /linux/Documentation/gpu/amdgpu/ |
| H A D | amdgpu-glossary.rst | 40 name stuck.
|
| /linux/Documentation/i2c/ |
| H A D | gpio-fault-injection.rst | 48 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/Documentation/process/ |
| H A D | botching-up-ioctls.rst | 113 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/tools/virtio/virtio-trace/ |
| H A D | README | 108 If a host does not open these, trace data get stuck in buffers of virtio. Then,
|
| /linux/Documentation/networking/device_drivers/ethernet/3com/ |
| H A D | vortex.rst | 233 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/Documentation/arch/arm64/ |
| H A D | asymmetric-32bit.rst | 29 altogether, so if you're stuck in the unenviable position of needing to
|
| /linux/Documentation/input/devices/ |
| H A D | atarikbd.rst | 194 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/drivers/usb/gadget/udc/ |
| H A D | net2280.c | 2605 int stuck = 0; in handle_ep_small() local
2645 req->td_dma && stuck++ > 5) { in handle_ep_small()
2651 ep->ep.name, stuck, in handle_ep_small()
2656 stuck = 0; in handle_ep_small()
2660 stuck = 0; in handle_ep_small()
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 135 are stuck in the initial patch state.
158 transition gets stuck for a long time because of a blocking task. Administrator
|
| H A D | reliable-stacktrace.rst | 48 code, and should not get stuck in an infinite loop or access memory in
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | nfs-rdma.rst | 28 If you get stuck, you can ask questions on the
|
| /linux/drivers/net/ethernet/myricom/myri10ge/ |
| H A D | myri10ge.c | 188 int stuck; member
3365 ss->stuck = 1; in myri10ge_check_slice()
3439 if (ss->stuck) { in myri10ge_watchdog()
3443 ss->stuck = 0; in myri10ge_watchdog()
|
| /linux/Documentation/filesystems/bcachefs/ |
| H A D | CodingStyle.rst | 34 we're not stuck debugging undefined behaviour should it turn out that you were
|
| /linux/Documentation/driver-api/ |
| H A D | dma-buf.rst | 337 - The compute workload might be stuck in a page fault, because the memory
|