wacom tablet unresponsive after xhci controller crash about input-wacom HOT 6 CLOSED

Have you tried only disabling power management on the Wacom device (i.e. something like /sys/module/wacom/drivers/hid:wacom/0003:056A:5146.*/power/control=on [or similar if wildcards aren't supported]?) With the controller dying like that its hard to say why our hardware isn't coming back up. We could potentially provide you with a version of input-wacom which more thoroughly debugs the probe() process to see if the kernel tries to reset the device afterwards and if so where exactly the driver has to fail.

from input-wacom.

Just tried it with power control set to on for wacom, and the xhci_hcd set to auto. Crashes don't happen with this configuration either but it is approximately 3 W/hr less efficient which is like a 50% increase in power usage. I didn't test this config for too long because it was so energy inefficient, but it was crash-free.

If you think it is worth debugging the driver I could help out.

from input-wacom.

I am also seeing "usb: port power management may be unreliable" in dmesg. I found this description of the issue which happens because the "kernel was unable to determine a port's peer". Seems like it could be related.

from input-wacom.

Sorry about the delay in responding... Its interesting that both you and #28 appear to be having issues with USB autosuspend. I'm not sure if something recently changed in the kernel, or if these particular devices have some kind of firmware bug.

I've added additional logging to our probe function that is called by the kernel when setting up a tablet. It should let us know if the kernel is even attempting to have us reconnect to the tablet after a crash, and if so roughly where its failing. Please clone a copy of my branch by running git clone https://github.com/jigpu/input-wacom.git -b issue-29 and then compiling/installing it like normal. Hopefully the dmesg log will contain a bit more information after the crash that will help us out.

from input-wacom.

Using this driver with all powertop settings to "good" and even though dmesg reports xHCI controller crashes:

[Sat Jun  9 12:03:33 2018] xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead
[Sat Jun  9 12:03:33 2018] xhci_hcd 0000:3c:00.0: remove, state 4
[Sat Jun  9 12:03:33 2018] usb usb3: USB disconnect, device number 1

The touchscreen keeps working unlike before. Note: I am on kernel 4.16.14-300.fc28.x86_64 (different from above).

Fedora by default is using wacom driver 2.00.36.1. I haven't tried using the stock driver with Fedora's more recent kernels, so it is possible this problem has been fixed by the kernel updates as opposed to the more recent wacom driver from your branch, will investigate further.

One thing- I can't permanently use this (or any more recent wacom driver that I compile myself) even after following instructions . Using dracut --force completes without error, but Fedora persists with the stock wacom kernel. I have to rmmod and modprobe (as described in troubleshooting) to load it.

from input-wacom.

I've used your github branch as well as the current stock driver in Fedora all weekend, and everything is working now even with all power saving features enabled. I am also not experiencing the lags described in #28. Closing. Happy to keep monitoring the logs if it helps in any way. Let me know.

from input-wacom.