You are not logged in.

#26 2020-04-18 16:05:39

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Post #16 details how to obtain linux-5.3.13.1-1  to test that version.  You can use the same method to check 5.4.  If it was introduced with 5.4 post #20 contains instructions to locate the causal commit.

Offline

#27 2020-04-20 11:06:19

gen2arch
Member
Registered: 2013-05-16
Posts: 182

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

loqs wrote:

Post #16 details how to obtain linux-5.3.13.1-1  to test that version.  You can use the same method to check 5.4.  If it was introduced with 5.4 post #20 contains instructions to locate the causal commit.

Hi loqs
sorry for the long absence, we are kind of having a hard time over here.
Actually I'm not sure if bisecting is an appropriate approach to this problem, as the non-functioning of the touchpad has a strong random moment to it: the fatal "lost-arbitration" error is not clear cut in its occurence (it occasionally happened already, though rarely, when I first got the machine last summer); it is more like a more-or-less-often thing, and this would deroute bisecting I guess.
Perhaps a better approach would be to directly contact the persons who dealt with this problem in 2016 (but how)?
Actually I also wrote a small patch increasing "2c-sda-hold-time-ns" to 1000ms and applied it every time I built a new custom kernel, but it didn't change things noticeably.
Thanks

Offline

#28 2020-04-20 11:09:19

gen2arch
Member
Registered: 2013-05-16
Posts: 182

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Haystack wrote:
anatolik wrote:

I had exactly the same error at my ThinkPad Yoga 4th Gen

i2c_designware i2c_designware.0: controller timed out

I googled a lot and tried different kernels/solution but nothing worked for me. Only after updating BIOS a few weeks ago the problem has gone away. So my suggestion is to update BIOS first using

fwupd

tool. And while we are here try Gnome Firmware Update app - it is really awesome and easy way to update firmware.

This didn't work for me, there were no updates available.

For me neither! it seems no updates whatsoever occur in fwupd for this machine!

Offline

#29 2020-04-21 13:27:26

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Have you tried the linux-i2c@vger.kernel.org mailing list?  See also https://www.kernel.org/doc/html/latest/ … -bugs.html

Last edited by loqs (2020-04-21 13:35:23)

Offline

#30 2020-06-13 01:06:41

Rigatavr
Member
Registered: 2020-06-13
Posts: 1

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Hi I'm aware that this has been inactive for a few months. Just wondering if anyone's found a definitive solution to the problem.
Also wanted to bring in some stuff that worked for me (potentially by accident) + some extra data.

Never had this problem on Windows. Started happening when I booted from a live kubuntu USB, and persisted in Windows when I rebooted into it.

The problem always disappears after the pc has been off for some time (overnight).

When booting into a manjaro live usb the problem happens less often if I don't skip the 10 second timer (it boots into the OS after the 10 seconds). What I haven't tried yet and which I'll try tomorrow is saying in that menu for an extra long time and then booting.

Also when it persisted on Windows, I did the booting into safe mode procedure (turn on and quickly off 3 times) but then juts selected to not go to safe mode and the problem was gone.

Anyway at least now I know there are others with the same issue.

Offline

#31 2020-06-24 11:03:51

olep
Member
Registered: 2020-06-08
Posts: 2

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

On my ideapad 5 14ARE05 I just had this problem in windows as well. However, it only occurs when hitting reboot in a defect linux state and then directly going into windows. Another fact I noticed is that the touchpad almost always fails on the next boot if
1. it failed on the current boot and
2. it it is constantly spamming me with "i2c_designware AMD:0010:00 controller timed out" when I try to shut it down in the current boot, so I have to long-press the power button.

This is pretty interesting since it proves that there is a way to shut down the touchpad correctly or incorrectly and that it has some kind of storage that persists. However, I did not find the exact startup/shutdown/restart procedure even though it should all be open source. It would be great if someone with a better knowledge of the linux kernel could help!

Offline

#32 2020-07-11 12:16:17

ThePiGuy
Member
Registered: 2020-03-06
Posts: 5

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Sorry for resurrecting the thread slightly, but I tried 5.8.0rc4 (actually via Fedora Rawhide live boot as I don't currently have linux installed due to this bug) and at least from the first boot, I get no designware errors any more (I used to get them even if the trackpad did actually work).

Offline

#33 2020-07-24 06:34:42

realsdx
Member
Registered: 2020-07-23
Posts: 1

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

I have the same issue on my Lenovo Yoga S740-14IIL. As ThePiGuy mentioned, i can also confirm that trackpad works on the Fedora rawhide (kernel 5.8.0-0.rc6.20200720git5714ee50bb43.1.fc33.x86_64) live boot. I think a regression fix was introduced in kernel 5.8-rc3 which fixed the issue. Maybe this is the particular PR that fixed the issue https://git.kernel.org/pub/scm/linux/ke … 91c9d563de.

Offline

#34 2020-07-24 16:26:17

ThePiGuy
Member
Registered: 2020-03-06
Posts: 5

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

realsdx wrote:

I have the same issue on my Lenovo Yoga S740-14IIL. As ThePiGuy mentioned, i can also confirm that trackpad works on the Fedora rawhide (kernel 5.8.0-0.rc6.20200720git5714ee50bb43.1.fc33.x86_64) live boot. I think a regression fix was introduced in kernel 5.8-rc3 which fixed the issue. Maybe this is the particular PR that fixed the issue https://git.kernel.org/pub/scm/linux/ke … 91c9d563de.

Glad to hear that seems to work for you too (especially with the same laptop as me!)

Just got to find a fix for the lack of FN key control/sleep/failure to power off without holding the power button. I suspect a lack of ACPI support...(which would also explain that patch as it seems to decouple the trackpad from ACPI?)

Offline

#35 2020-08-05 17:09:50

ThePiGuy
Member
Registered: 2020-03-06
Posts: 5

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Has anybody tried the 5.8.arch1-1 kernel that's currently in testing to see if this does actually fix the issue?

Edit: I decided to try myself and sadly on the 5.8.arch1-1 kernel, my touchpad is as dead as it was before.

The errors are differerent (it just says timed out now) but it still doesn't work

Last edited by ThePiGuy (2020-08-05 18:37:08)

Offline

#36 2020-10-26 00:30:13

pkedzierski
Member
Registered: 2020-10-25
Posts: 1

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Hello
I have Dell Inspiron 15.
My synaptics touchpad dies after a few minutes with warning: i2c_designware 808622C1:00: i2c_dw_handle_tx_abort: lost arbitration
I suppose this is a problem with i2c bus (or connections of wires from touchpad).
If I try to run i2c bus with low frequency (i2c_bus=0,100 in kernel command line) it sometimes works.

Offline

#37 2020-11-02 10:33:52

jmesa
Member
Registered: 2020-11-01
Posts: 1

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Hi, the only workaround that I have found to work is to suspend it:

[    3.644620] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator
[    3.644649] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy regulator
[    5.488330] i2c_hid i2c-MSFT0001:00: failed to retrieve report from device.
[    5.488386] input: MSFT0001:00 06CB:CDB0 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-MSFT0001:00/0018:06CB:CDB0.0001/input/input9
[    5.488541] input: MSFT0001:00 06CB:CDB0 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-MSFT0001:00/0018:06CB:CDB0.0001/input/input10
[    5.488785] hid-generic 0018:06CB:CDB0.0001: input,hidraw1: I2C HID v1.00 Mouse [MSFT0001:00 06CB:CDB0] on i2c-MSFT0001:00
[    6.554988] i2c_hid i2c-MSFT0001:00: failed to retrieve report from device.
[    7.568290] i2c_hid i2c-MSFT0001:00: failed to retrieve report from device.
[    8.581659] i2c_hid i2c-MSFT0001:00: failed to retrieve report from device.
[    9.595010] i2c_hid i2c-MSFT0001:00: failed to retrieve report from device.
[    9.595087] input: MSFT0001:00 06CB:CDB0 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-MSFT0001:00/0018:06CB:CDB0.0001/input/input23
[    9.595239] input: MSFT0001:00 06CB:CDB0 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-MSFT0001:00/0018:06CB:CDB0.0001/input/input24
[    9.595396] hid-multitouch 0018:06CB:CDB0.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 06CB:CDB0] on i2c-MSFT0001:00
[   10.608304] i2c_hid i2c-MSFT0001:00: failed to set a report to device.
[   11.621667] i2c_hid i2c-MSFT0001:00: failed to set a report to device.
[   12.635001] i2c_hid i2c-MSFT0001:00: failed to set a report to device.
...suspend...
...wake up...
[  105.728626] i2c_hid i2c-MSFT0001:00: failed to change power setting.

Every time I login the touchpad doesn't work, but If i suspend the laptop and wake up it, it works without problems. That confirm is power configuration related...

Linux udontknowme 5.8.16-2-MANJARO #1 SMP PREEMPT Mon Oct 19 11:33:03 UTC 2020 x86_64 GNU/Linux
Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL

Offline

#38 2021-02-22 11:04:36

gen2arch
Member
Registered: 2013-05-16
Posts: 182

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Hi everyone,

so it would seem that this very long standing bug is solved! That is great!

On none of my machines that had this touchpad malfunction ("arbitration lost" errors on the  i2c bus) did it ever re-occur. I guess this vanished sometime around November/December.

I didn't change anything on my side, so I guess this was solved in the kernel.

Can someone affirm that (point to a i2c specific commit)? Thanks

Offline

#39 2021-02-26 14:05:48

gen2arch
Member
Registered: 2013-05-16
Posts: 182

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Closing this now, as it seems solved upstream.
Thanks!

Offline

#40 2022-11-11 15:46:13

eomanis
Member
Registered: 2013-04-17
Posts: 50

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

Oh, damn, I just got this error again on linux-6.0.7 on an HP Elite x2 1012 G1 I bought a few days ago, and the touch screen stopped working.

Nov 11 14:38:15 my-tablet kernel: i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost arbitration
Nov 11 14:38:16 my-tablet kernel: i2c_designware i2c_designware.0: controller timed out

This appears to still happen intermittently, so whatever upstream fix there is, it is not perfect.
The touch screen fixed itself though while I was reading this thread using the keyboard and touchpad of the attached cover. No kernel log entry for when that happened though.

Offline

#41 2024-01-27 22:08:55

smallberries.john
Member
Registered: 2020-11-19
Posts: 5

Re: SOLVED: What is i2c_designware and why does it ruin my touchpad?

I realize that this is an old thread and I don't want to necrobump, but for people like me who have Acer Nitro 5s, the problem is overheating. When I run Linux, I'm fine, but after I play a game on Windows 10 (and NBFC ramps up the fan speed) and then come back to Linux, the trackpad conks out. Sometimes it'll come back to life after re-installing the "BIOS" firmware, but that's only because of the HEAT produced when the bios does the actual upgrading after a reboot. The fan goes full blast. It's not the fault of the kernel because I've had it conk out in 6.1.70 and 5.6.0-2 (in Devuan).

It's our lousy hardware.

Offline

Board footer

Powered by FluxBB