[Bug 638506] New: Wacom graphire 3 (CTE-430) is not working with new kernel 2.6.34.4-0.1.1
https://bugzilla.novell.com/show_bug.cgi?id=638506 https://bugzilla.novell.com/show_bug.cgi?id=638506#c0 Summary: Wacom graphire 3 (CTE-430) is not working with new kernel 2.6.34.4-0.1.1 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: sergey1369@narod.ru QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 After update to kernel-2.6.34.4-0.1.1 Xorg server hangs on startup with black screen. Hotplugging works normally. Last lines in Xorg.0.log on newer kernel: [ 36.468] (II) config/udev: Adding input device Wacom Graphire3 (/dev/input/event4) [ 36.468] (**) Wacom Graphire3: Applying InputClass "evdev tablet catchall" [ 36.468] (**) Wacom Graphire3: Applying InputClass "Wacom Tablet" [ 36.468] (II) LoadModule: "wacom" [ 36.469] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so [ 36.481] (II) Module wacom: vendor="X.Org Foundation" [ 36.481] compiled for 1.8.0, module version = 0.10.5 [ 36.481] Module class: X.Org XInput Driver [ 36.481] ABI class: X.Org XInput driver, version 9.0 [ 36.481] (**) Option "Device" "/dev/input/event4" Last lines in Xorg.0.log on old kernel 2.6.34-12.3 [ 60.809] (II) LoadModule: "wacom" [ 60.810] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so [ 60.822] (II) Module wacom: vendor="X.Org Foundation" [ 60.822] compiled for 1.8.0, module version = 0.10.5 [ 60.822] Module class: X.Org XInput Driver [ 60.822] ABI class: X.Org XInput driver, version 9.0 [ 60.822] (**) Option "Device" "/dev/input/event4" [ 60.825] (II) Wacom Graphire3: type not specified, assuming 'stylus'. [ 60.825] (II) Wacom Graphire3: other types will be automatically added. [ 60.825] (**) Wacom Graphire3: always reports core events [ 60.825] (II) Wacom Graphire3: hotplugging dependent devices. [ 60.825] (**) Option "Device" "/dev/input/event4" [ 60.827] (**) Wacom Graphire3 eraser: always reports core events [ 60.829] (II) XINPUT: Adding extended input device "Wacom Graphire3 eraser" (type: ERASER) [ 60.837] (--) Wacom Graphire3 eraser: using pressure threshold of 30 for button 1 [ 60.837] (--) Wacom Graphire3 eraser: Wacom USB Graphire3 tablet speed=38400 maxX=10208 maxY=7424 maxZ=511 resX=2032 resY=2032 tilt=disabled [ 60.837] (--) Wacom Graphire3 eraser: top X=0 top Y=0 bottom X=10208 bottom Y=7424 resol X=2032 resol Y=2032 [ 60.837] (**) Option "Device" "/dev/input/event4" [ 60.839] (**) Wacom Graphire3 cursor: always reports core events [ 60.841] (II) XINPUT: Adding extended input device "Wacom Graphire3 cursor" (type: CURSOR) [ 60.841] (--) Wacom Graphire3 cursor: top X=0 top Y=0 bottom X=10208 bottom Y=7424 resol X=2032 resol Y=2032 [ 60.841] (II) Wacom Graphire3: hotplugging completed. [ 60.845] (II) XINPUT: Adding extended input device "Wacom Graphire3" (type: STYLUS) [ 60.845] (--) Wacom Graphire3: top X=0 top Y=0 bottom X=10208 bottom Y=7424 resol X=2032 resol Y=2032 [ 60.845] (II) config/udev: Adding input device Wacom Graphire3 (/dev/input/mouse0) [ 60.845] (**) Wacom Graphire3: Applying InputClass "Wacom Tablet" [ 60.845] (**) Option "Device" "/dev/input/mouse0" [ 60.849] (EE) Wacom Graphire3: wcmDeviceTypeKeys unable to ioctl USB key bits. [ 60.853] (II) UnloadModule: "wacom" [ 60.853] (EE) PreInit returned NULL for "Wacom Graphire3" .... unrelevant lines skipped ..... Reproducible: Always Steps to Reproduce: 1. zypper in kernel-desktop-2.6.34.4-0.1.1 2. reboot Actual Results: Server hangs with black screen. Expected Results: Server login dialog. wacom.ko seems same in both kernels, so problem is not module related. Known workarounds: Do not use newer kernel. zypper in -f kernel-desktop-2.6.34-12.3 zypper addlock kernel-desktop reboot Hotplug after boot. - disconnect tablet - load Xorg, get login dialog - Connect tablet -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c1
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c2
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c3
--- Comment #3 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c4
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c5
Jiri Slaby
info when X is starting, except it is in D state, probably trying to read wacom input event.
Could you do: echo t >/proc/sysrq-trigger and attach the trace of X from .34.4? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c6
--- Comment #6 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c7
--- Comment #7 from Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c8
Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c9
Jiri Slaby
sysrq-tigger enabled just before "rcxdm start"
No, I need a trace of X. So you have to do it after X starts (and hangs). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c10
--- Comment #10 from Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c11
Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c12
Jiri Slaby
Created an attachment (id=389147) --> (http://bugzilla.novell.com/attachment.cgi?id=389147) [details] dmesg after Xorg hangs and task list requested
Thanks. Nice example of AA deadlock: [<ffffffff814a00ea>] mutex_lock+0x1a/0x40 [<ffffffffa02bc94b>] wacom_resume+0x3b/0x90 [wacom] [<ffffffff81327a32>] usb_resume_interface+0xd2/0x190 [<ffffffff81327b5d>] usb_resume_both+0x6d/0x110 [<ffffffff81327c24>] usb_runtime_resume+0x24/0x40 [<ffffffff8130a2cf>] __pm_runtime_resume+0x26f/0x450 [<ffffffff8130a23a>] __pm_runtime_resume+0x1da/0x450 [<ffffffff8130a53a>] pm_runtime_resume+0x2a/0x50 [<ffffffff81328176>] usb_autopm_get_interface+0x26/0x60 [<ffffffffa02bc626>] wacom_open+0x36/0x90 [wacom] wacom_open took wacom->lock and calls usb_autopm_get_interface which in turn calls wacom_resume which tries to aquire the lock again. Is it better with kernel from: http://labs.suse.cz/jslaby/bug-638200/ which turns runtime suspend back off? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c13
Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c14
--- Comment #14 from Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c15
--- Comment #15 from Jiri Slaby
This set /sys/bus/usb/devices/*/power/level to "on" for any wacom usb device. After this Xorg works normally (for me).
Yes, it should help generally. Actually I wonder, why usbcore.autosuspend=0 didn't help you... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c16
--- Comment #16 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c17
--- Comment #17 from Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c18
--- Comment #18 from Bernd Paysan
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c19
Bernd Paysan
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c20
--- Comment #20 from Sergey -
https://bugzilla.novell.com/show_bug.cgi?id=638506
https://bugzilla.novell.com/show_bug.cgi?id=638506#c21
Jiri Slaby
participants (1)
-
bugzilla_noreply@novell.com