Created attachment 697752 [details] Xorg.0.log section after boot (when it works) Description of problem: Wacom (Intuos4) tablet works fine if plugged in during boot. Attempts to hotplug the tablet fail. Version-Release number of selected component (if applicable): 3.7.3-101.fc17.x86_64 How reproducible: Very Steps to Reproduce: 1. Boot with wacom - works 2. Unplug USB cable 3. Replug USB cable - no longer works Actual results: No activity from tablet, stylus, buttons, etc. Expected results: Normal activity Additional info: Rolled back to earlier kernel on the same machine and it worked fine.
Created attachment 697753 [details] Relevant Xorg.0.log section after hotplug.
I can confirm this bug. I have a wacom bamboo, but my tablet is not working with 3.7 kernels at all, neither with plug at boot or hotplug. The software can "see" it but no reactions. 3.6 kernels work perfectly. Also this bug is present in Fedora 17 and in i686 arch. (I was reinstalled my system at this weekend.) So the problem is in 3.7.x kernels.
This may be a linuxwacom driver issue. See here: http://comments.gmane.org/gmane.linux.drivers.wacom/6588
(In reply to comment #3) > This may be a linuxwacom driver issue. See here: > > http://comments.gmane.org/gmane.linux.drivers.wacom/6588 The commit for that wound up being: commit 9937c026820baabd1e908a9c1e6bdc846293000a Author: Chris Bagwell <chris> Date: Wed Jan 23 19:37:34 2013 -0800 Input: wacom - fix wacom_set_report retry logic Logic sets a value and then reads it back to make sure it worked and retries write on failures. Since read and write share a buffer, it needs to be set back up before writing though. Issue is not seen a lot because 1) it doesn't need to retry for a lot of tablets and 2) a lot of failures that need a retry are from an -ETIMEDOUT and hopefully buffer is not touched in this case. At least one user has shown logs with buffer being modified during -ETIMEDOUT case with linux 3.7 kernel. Signed-off-by: Chris Bagwell <chris> Signed-off-by: Dmitry Torokhov <dmitry.torokhov> which was included in the 3.8 kernel. We have 3.8.2 in updates-testing for F17. Could you please try that and let us know if it fixes this issue?
Confirmed the fix in 3.8 kernel (in F18). Thanks for this.
Great, thanks for letting us know.
kernel-3.8.2-105.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2013-3638/kernel-3.8.2-105.fc17
kernel-3.8.3-101.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kernel-3.8.3-101.fc17
Confirmed the fix too.
Package kernel-3.8.3-101.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.8.3-101.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3909/kernel-3.8.3-101.fc17 then log in and leave karma (feedback).
kernel-3.8.3-103.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.