| /linux/Documentation/devicetree/bindings/i2c/ | 
| H A D | i2c-mux-pca954x.yaml | 74   maxim,isolate-stuck-channel:76     description: Allows to use non faulty channels while a stuck channel is
 82     description: Send a flush-out sequence to stuck auxiliary buses
 83       automatically after a stuck channel is being detected.
 88       register activates a channel to detect a stuck high fault. On fault the
 124         maxim,isolate-stuck-channel: false
 
 | 
| /linux/drivers/net/wireless/mediatek/mt76/mt7603/ | 
| H A D | debugfs.c | 11 		[RESET_CAUSE_TX_BUSY] = "TX DMA busy stuck",  in mt7603_reset_read()12 		[RESET_CAUSE_RX_BUSY] = "RX DMA busy stuck",  in mt7603_reset_read()
 13 		[RESET_CAUSE_RX_PSE_BUSY] = "RX PSE busy stuck",  in mt7603_reset_read()
 14 		[RESET_CAUSE_BEACON_STUCK] = "Beacon stuck",  in mt7603_reset_read()
 
 | 
| /linux/Documentation/devicetree/bindings/sound/ | 
| H A D | adi,max98396.yaml | 81   adi,dmon-stuck-enable:83       Enables the "data monitor stuck" feature. Once the data monitor is
 89   adi,dmon-stuck-threshold-bits:
 91       Sets the threshold for the "data monitor stuck" feature, in bits.
 
 | 
| /linux/drivers/input/keyboard/ | 
| H A D | pmic8xxx-keypad.c | 84  * @key_stuck_irq: key stuck notification irq number88  * @stuckstate: present state when key stuck irq
 318  * whenever key-stuck interrupt happens, because events counter doesn't
 319  * get updated when this interrupt happens due to key stuck doesn't get
 323  * because it might report the key which was pressed before the key being stuck
 324  * as stuck key because it's pressed status is stored in the old data
 492  * only, otherwise it might get into FSM stuck state.
 599 			"pmic-keypad-stuck", kp);  in pmic8xxx_kp_probe()
 601 		dev_err(&pdev->dev, "failed to request keypad stuck irq\n");  in pmic8xxx_kp_probe()
 
 | 
| /linux/Documentation/ABI/testing/ | 
| H A D | sysfs-class-bdi | 70 	mount that is prone to get stuck, or a FUSE mount which cannot83 	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/fs/xfs/ | 
| H A D | xfs_trans_ail.c | 470 	int			stuck = 0;  in xfsaild_push()  local550 			stuck++;  in xfsaild_push()
 557 			stuck++;  in xfsaild_push()
 579 		if (stuck > 100)  in xfsaild_push()
 607 	} else if (((stuck + flushing) * 100) / count > 90) {  in xfsaild_push()
 610 		 * stuck due to operations in progress. "Stuck" in this case  in xfsaild_push()
 611 		 * is defined as >90% of the items we tried to push were stuck.  in xfsaild_push()
 616 		 * the restart to issue a log force to unpin the stuck items.  in xfsaild_push()
 
 | 
| /linux/include/uapi/linux/ | 
| H A D | xilinx-v4l2-controls.h | 45 /* Enable a stuck pixel feature */69 /* Upper limit count of generated stuck pixels */
 
 | 
| /linux/Documentation/hwmon/ | 
| H A D | asus_wmi_sensors.rst | 70    fans stopping, fans getting stuck at max speed, or temperature readouts71    getting stuck. This is not an issue with the driver, but the BIOS. The Prime
 
 | 
| /linux/drivers/i2c/algos/ | 
| H A D | i2c-algo-pca.c | 327 		case 0x70: /* Bus error - SDA stuck low */  in pca_xfer()328 			DEB2("BUS ERROR - SDA Stuck low\n");  in pca_xfer()
 331 		case 0x78: /* Bus error - SCL stuck low (PCA9665) */  in pca_xfer()
 332 		case 0x90: /* Bus error - SCL stuck low (PCA9564) */  in pca_xfer()
 333 			DEB2("BUS ERROR - SCL Stuck low\n");  in pca_xfer()
 
 | 
| H A D | i2c-algo-bit.c | 37 MODULE_PARM_DESC(bit_test, "lines testing - 0 off; 1 report; 2 fail if stuck");256 		pr_warn("%s: SDA stuck high!\n", name);  in test_bus()
 266 		pr_warn("%s: SDA stuck low!\n", name);  in test_bus()
 276 		pr_warn("%s: SCL stuck high!\n", name);  in test_bus()
 286 		pr_warn("%s: SCL stuck low!\n", name);  in test_bus()
 464  *	-ETIMEDOUT, for example if the lines are stuck...)
 
 | 
| /linux/drivers/usb/host/ | 
| H A D | ehci-platform.c | 136  * stuck very rarely after a full/low usb device was disconnected. To140  * Return: true if the controller's port_status indicated getting stuck
 160  * stuck very rarely after a full/low usb device was disconnected. To
 195 	ehci_dbg(ehci, "%s: detected getting stuck. rebind now!\n", __func__);  in quirk_poll_work()
 
 | 
| /linux/Documentation/process/ | 
| H A D | botching-up-ioctls.rst | 113    now we're stuck forever with some arcane semantics in both the kernel and116  * 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/perf/tests/ | 
| H A D | tests.h | 188  * handler to avoid stepping into the SIGIO handler and getting stuck on the192  * case also gets stuck on the breakpointed instruction.
 
 | 
| /linux/drivers/gpu/drm/i915/gt/ | 
| H A D | intel_engine_heartbeat.c | 19  * is stuck, and we fail to preempt it, we declare the engine hung and182 			 * context are stuck waiting for the signal.  in heartbeat()
 214 		/* Unable to lock the kernel timeline, is the engine stuck? */  in heartbeat()
 
 | 
| /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 release50 device deglitching and monitoring the I2C bus. It could also detect a stuck SDA
 
 | 
| /linux/drivers/i2c/busses/ | 
| H A D | i2c-pasemi-core.c | 103 		dev_err(smbus->dev, "Bus is still stuck (status 0x%08x xfstatus 0x%08x)\n",  in pasemi_smb_clear()169 	/* Still stuck in a transaction? */  in pasemi_smb_waitready()
 171 		dev_err(smbus->dev, "Bus stuck, status 0x%08x\n", status);  in pasemi_smb_waitready()
 
 | 
| H A D | i2c-ali15x3.c | 240 	   I've tried the following to reset a stuck busy bit.  in ali15x3_transaction()256 	   If that's the case you are stuck.  in ali15x3_transaction()
 271 			   as one of the bits now appears to be stuck */  in ali15x3_transaction()
 
 | 
| /linux/drivers/input/touchscreen/ | 
| H A D | exc3000.c | 175 	 * We read full state successfully, no contacts will be "stuck".  in exc3000_handle_mt_event()193 	/* Schedule a timer to release "stuck" contacts */  in exc3000_handle_mt_event()
 207 		/* Schedule a timer to release "stuck" contacts */  in exc3000_interrupt()
 
 | 
| /linux/drivers/net/fddi/skfp/ | 
| H A D | rmt.c | 325 				 * lost we need to restart the stuck timer to  in rmt_fsm()326 				 * check the "stuck beacon" condition.  in rmt_fsm()
 403 				 * lost we need to restart the stuck timer to  in rmt_fsm()
 404 				 * check the "stuck beacon" condition.  in rmt_fsm()
 
 | 
| /linux/drivers/gpu/drm/xe/ | 
| H A D | xe_hw_engine_group_types.h | 29  * that prevents them from making progress when one is stuck on a page fault.
 | 
| /linux/kernel/ | 
| H A D | smp.c | 216  * csd_lock_is_stuck - Has a CSD-lock acquisition been stuck too long?218  * Returns @true if a CSD-lock acquisition is stuck and has been stuck
 252 	/* How long since we last checked for a stuck CSD lock.*/  in csd_lock_wait_toolong()
 276 	/* How long since this CSD lock was stuck. */  in csd_lock_wait_toolong()
 285 	 * If the CSD lock is still stuck after 5 minutes, it is unlikely  in csd_lock_wait_toolong()
 
 | 
| /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/include/dt-bindings/clock/ | 
| H A D | bcm281xx.h | 17  * We're stuck with using "bcm11351" in the string because wild
 | 
| /linux/tools/testing/selftests/sched_ext/ | 
| H A D | exit.c | 27 		 * invoked, so skip this test to avoid getting stuck  in run()
 | 
| /linux/arch/arm64/kernel/ | 
| H A D | machine_kexec.c | 53  * are stuck in the kernel. This avoids a panic once we hit machine_kexec().58 		pr_err("Can't kexec: CPUs are stuck in the kernel.\n");  in machine_kexec_prepare()
 
 |