Bug 215345 - ACPI issues break ELAN071B:00 touchpad: sometimes working after restarting i2c_hid_acpi - AMD Ryzen 7 4700U with Radeon Graphics
Summary: ACPI issues break ELAN071B:00 touchpad: sometimes working after restarting i2...
Status: NEW
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: acpi_acpica-core@kernel-bugs.osdl.org
Depends on:
Reported: 2021-12-17 03:34 UTC by coronagraph
Modified: 2022-05-26 05:35 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.17.11
Regression: No
Bisected commit-id:

tarball of /sys/firmware/acpi (101.72 KB, application/x-bzip)
2021-12-17 03:34 UTC, coronagraph
dmesg output (from kernel 5.15.7, but has same errors as in 5.15.9) (87.70 KB, text/plain)
2021-12-17 03:36 UTC, coronagraph

Description coronagraph 2021-12-17 03:34:12 UTC
Created attachment 300047 [details]
tarball of /sys/firmware/acpi


I wasn't sure whether to file this in ACPICA-Core, BIOS, or Config-Tables

I have an HP Probook X360 435 g7 with an "ELAN071B:00 04F3:312C Touchpad"
The touchpad usually works fine, but sometimes it stops working either during reboot or after wake from suspend. I thought the issue might be related to runtime power-management, but I set power/control to "on" with a udev rule for my touchpad, and it can still stop working after wake and boot. 
Additionally, my touchpad sometimes gets detected as a mouse, disabling features like scrolling and disable while typing.

Since restarting the i2c_hid_acpi module sometimes fixes the issue, I thought the issue might be related to i2c. I now think it's more likely to be an ACPI issue, though, because I get some ACPI errors during boot and because I also have a less frequent issue where my screen doesn't turn on after wake from suspend. 

While booting I always get this error (which does not break the touchpad):
ACPI BIOS ERROR (bug): Could not resolve symbol [\_SB.PCI0.BUSB.SAT1], AE_NOT_FOUND (20210730/dswload2-162)
ACOU Error: AE_NOT_FOUND, During name lookup/catalog (20210730,psobject-220)

That error doesn't seem to be directly causing any issues because everything still works fine. However, I sometimes get the below error during boot, causing my touchpad to fail:
hid(null): reading report descriptor failed
i2c_hid_acpi i2c-ELAN071B:00: can't add hid device: -5

I also get this error in dmesg which seems relevant because it mentions "SystemIO":
ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B06 (\_SB.PCI0.SMBS.SMBO) (20210730/utaddress-204)

Attached is a tarball of /sys/firmware/acpi (which includes the tables)
Comment 1 coronagraph 2021-12-17 03:36:16 UTC
Created attachment 300049 [details]
dmesg output (from kernel 5.15.7, but has same errors as in 5.15.9)
Comment 2 coronagraph 2021-12-17 03:37:38 UTC
Expected behavior: 
Touchpad always works normally, after boot and wake from suspend

Actual behavior:
Touchpad randomly freezes after boot or wake from suspend and is sometimes detected as a mouse.

Steps to reproduce:
None, seems random, but will often persist for a few reboots after it starts happening
Comment 3 coronagraph 2022-01-15 04:23:52 UTC
Changed to config-tables because a lot of ELANTECH touchpad issues seem to cite bugs in the acpi tables, still not 100% sure what those do
Comment 4 coronagraph 2022-01-30 21:42:14 UTC
Apparently i2c_hid_acpi relies on pinctrl_amd, so that might be of importance too.

I also get this error:
i2c_hid_acpi i2c-ELAN071B:00: failed to set a report to device.

It happens periodically while the laptop is on and doesn't seem to stop the touchpad from working on its own.

Note You need to log in before you can comment on or make changes to this bug.