UNSOLVED

whatno

updated

1 month ago

W

whatno

1 Rookie

•

1 Message

•

4 Points

0

57

October 4th, 2026 15:06

Dell XPS 13 9350: Elan Touchpad (VEN_04F3) freezes after s2idle sleep following System Firmware 1.25.0 update

Disclaimer. This is an AI summary of a bug I encountered today after the firmware update from yesterday. I'm a real human being, though. I swear. All fireware and software is as new as it can be.

 

Dell Inc. XPS 13 9350

Ubuntu 26.04.1 LTS

Intel® Core™ Ultra 7 256V × 8

Linux 7.0.0-38-generic

 

After updating the System Firmware on the Dell XPS 13 9350 (2024 / Intel Core Ultra) from v1.22.0 to v1.25.0, the Elan Touchpad (i2c-VEN_04F3:00) ceases to function properly after resuming from prolonged s2idle sleep (suspend-to-idle).

While the cursor movement via HID sometimes remains active, multi-touch gestures and click events fail to register completely.

Expected Behavior:

The touchpad should fully resume and respond to clicks and gestures immediately after waking up from s2idle.

Actual Behavior:

Following s2idle sleep exceeding ~15–30 minutes, the touchpad IRQ/event handler fails to re-initialize. A session logout or reloading the I2C modules (modprobe -r i2c_hid_acpi i2c_hid && modprobe i2c_hid_acpi) temporarily restores functionality until the next sleep cycle.

Root Cause Analysis:

The issue appears to be an ACPI / Runtime Power Management regression introduced in System Firmware 1.25.0. The new UEFI update forces the Intel DesignWare I2C controller (0000:00:15.2) and the Elan touchpad into an aggressive low-power state during s2idle from which the Linux kernel fails to wake the device.

System Environment:

  • Laptop Model: Dell XPS 13 9350 (2024)

  • OS: Ubuntu 26.04 LTS (Kernel: 6.x)

  • Touchpad Hardware: Elan Microelectronics (i2c-VEN_04F3:00 via i2c_designware.1)

  • Firmware Version: System Firmware 1.25.0 (Updated via fwupd / LVFS)

  • Suspend Mode: s2idle (/sys/power/mem_sleep)

Workaround / Fix Verification:

Disabling Runtime PM (Autosuspend) for the I2C device and parent PCI bridge completely resolves the issue without needing module resets:

Bash
echo "on" | sudo tee /sys/bus/i2c/devices/i2c-VEN_04F3:00/power/controlecho "on" | sudo tee /sys/bus/pci/devices/0000:00:15.2/power/control

Setting power/control to on keeps the I2C bus responsive after wake-up, confirming that aggressive firmware-level Power-Gating in 1.25.0 is preventing proper IRQ resume.

 
No Responses