Wacom touchscreen not working after resume

When executing xinput --list after resume, entries for the touch screen, pen and eraser do not show in the list. The do show on initial boot.

I also have this problem. Since I use the tablet functions for work, it makes 11.04 a huge regression - the tablet has to be rebooted each and every time. I've also noticed the usb ports on the right side stop functioning after a suspend and resume (I have a wireless mouse attached during suspend). Coupled with the random crashes of the radeon driver on reboot and a much more flaky monitor support (no longer possible to have external vga screen side by side, can't change orientation of screen) this makes 11.04 a disaster on an HP tm2.

I confirm the problem with right-side usb-ports. Both problems are reproduced on 2.6.39-3 kernel from oneiric.

This bug still present with oneiric 3.0.0-11-generic and 3.0.0-12-generic. It makes the whole distribution painful to use a tablet requires a reboot each and every time and oneiric gives a kernel oops more often than not with a Radeon card due to other bugs.

can it's importance be set to high?

This bug is still present with 3.0.0-13-generic. No tablet after resume.

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

Just tested it with 3.1.0-999.201110210416. The problem remains.

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Umm, sorry?
Brad, Joseph has tested the kernel 3.0.0-13.21, which is obviously newer than 3.0.0-12.20. And I've tested it with the yesterday daily 3.1.0 build. Please, indicate what newer kernel should we test with?

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Hi Vsevolod

The request to test the 3.0.0-12.20 kernel is an automated script. It triggers off the kernel-request-3.0.0-12.20 tag, so thats why you got a duplicate request when you removed that tag.

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Joseph, thanks for your explanation. I've just tried to file a bug, however... bugzilla.kernel.org isn't responding at all.
If someone other can access it (I hope, it's some local network problem), please, file the bug instead of me.

Yes, it appears that bugzilla.kernel.org is still unavailable. One alternative would be to report this directly to the subsystem maintainer or to the Linux Kernel Mailing List - <email address hidden>

After some investigation this appears to be a problem with usb and the loss of the wacom devices is a side effect.

See here: http://forums.opensuse.org/english/get-technical-help-here/hardware/467080-wacom-devices-lost-after-resume-11-4-a.html

Note this problem is present in openSUSE 11.4 which runs kernel 2.6.37.6, so it came in somewhere between 2.6.35 and 2.6.37.

PARTIAL-FIX (workaround):

I compiled a 2.6.37.6 kernel with uhci_hcd and ehci_hcd as modules. After resume the wacom devices (and right-side usb) can be revived by rmmod uhci_hcd; modprobe uhci_hcd

The issue is a power management issue with usb. Not sure what changed from 2.6.35 to cause this.

The bug seems to be fixed at least in kernel ppa build 3.2.0-999.201111130405.

Alexei,

Can you test the 3.2 kernel, and see if your issue is fixed like it is for Vsevolod? The kernel is available from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc1-oneiric/

I had the same problem with my Intuos2 tablet and by adding the line:
SUSPEND_MODULES="wacom psmouse"

to the file "/etc/pm/config.d/unload_modules", the problem was solved.

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.