Bug 219340

Summary: Bug Report: Keyboard Lag When Ejecting or Plugging AC Power Cord into Thunderbolt 4 Port
Product: ACPI Reporter: kevinroan0303
Component: ACPICA-CoreAssignee: acpi_acpica-core (acpi_acpica-core)
Status: NEW ---    
Severity: normal    
Priority: P3    
Hardware: All   
OS: Linux   
Kernel Version: Subsystem:
Regression: No Bisected commit-id:

Description kevinroan0303 2024-10-01 18:09:03 UTC
I am experiencing intermittent keyboard input lag when I eject or plug the AC power cord into the Thunderbolt 4 port on my HP laptop running Arch Linux with the latest stable kernel version (6.11.1). This issue does not occur in Windows, and a reboot temporarily resolves the problem.

**System Information:**
- Distribution: Arch Linux (rolling release)
- Kernel Version: 6.11.1-stable
- System: HP laptop with Intel i5-12500H processor
- Thunderbolt Port: Thunderbolt 4
- Issue Location: Occurs both in X sessions and in a tty
- Environment: No external devices connected (except for power supply)

**Steps to Reproduce:**
1. Boot into Arch Linux with kernel 6.11.1.
2. Unplug or plug the AC power cord into the Thunderbolt 4 port.
3. Observe intermittent keyboard input lag immediately after the action.

**Additional Information:**
- I noticed the following error message in the logs:
  [ 1695.836166] ucsi_acpi USBC000:00: GET_CONNECTOR_STATUS failed (-110)
- The keyboard input lag disappears after a reboot, but returns when ejecting or plugging the AC power cord again.
- This issue did not occur under the OEM Windows installation.

**Logs & Diagnostics:**
- Kernel log when the issue occurs:
  [ 1695.836166] ucsi_acpi USBC000:00: GET_CONNECTOR_STATUS failed (-110)

**Expected Behavior:**
There should be no keyboard input lag when ejecting or plugging the AC power cord into the Thunderbolt 4 port.

**Actual Behavior:**
The keyboard becomes unresponsive, and input is delayed, requiring a reboot to temporarily fix the issue.

**Additional Context:**
- TLP and power management tools like cpupower are disabled.
- The problem persists across multiple X session configurations and also in tty mode.
- Full reboot resolves the issue temporarily.

---\