Bug 1186785 - [Regression] USBest Technology SiS HID Touch Controller does not work after resume from suspend
Summary: [Regression] USBest Technology SiS HID Touch Controller does not work after r...
Keywords:
Status: CLOSED DUPLICATE of bug 1173849
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-evdev
Version: 21
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-28 14:33 UTC by Milan Bouchet-Valat
Modified: 2015-01-28 15:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-28 15:19:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (including suspend-resume cycle) (72.72 KB, text/plain)
2015-01-28 14:33 UTC, Milan Bouchet-Valat
no flags Details
xinput list (993 bytes, text/plain)
2015-01-28 14:35 UTC, Milan Bouchet-Valat
no flags Details

Description Milan Bouchet-Valat 2015-01-28 14:33:18 UTC
Created attachment 985197 [details]
dmesg (including suspend-resume cycle)

This used to work on latest Fedora 20. On F21, the touchscreen works fine on fresh boot, but after suspend it stops responding. rmmod hid_multitouch && modprobe hid_multitouch fixes the problem.

It doesn't look like the bug comes from the kernel, as booting with 3.17.8 from F20 (with all packages from F21) does not fix the problem.

There are errors related to the touchscreen in dmesg (see below and attached file).

Please ask if you need anything else.


$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                  id=14   [slave  pointer  (2)]
⎜   ↳ USBest Technology SiS HID Touch Controller        id=10   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=12   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=13   [slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam                      id=11   [slave  keyboard (3)]


Relevant excerpt from dmesg output (see attached file):
janv. 28 14:39:49 pc-ses kernel: done.
janv. 28 14:39:49 pc-ses kernel: usb 1-3: USB disconnect, device number 5
janv. 28 14:39:49 pc-ses kernel: Restarting tasks ... 
janv. 28 14:39:49 pc-ses kernel: PM: Finishing wakeup.
janv. 28 14:39:49 pc-ses kernel: PM: resume of devices complete after 1261.383 msecs
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801394c9f60
janv. 28 14:39:49 pc-ses kernel: usb 1-4: reset high-speed USB device number 4 using xhci_hcd
janv. 28 14:39:49 pc-ses kernel: usb 1-4: hub failed to enable device, error -22
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
janv. 28 14:39:49 pc-ses kernel: usb 1-4: reset high-speed USB device number 4 using xhci_hcd
janv. 28 14:39:49 pc-ses kernel: usb 1-4: hub failed to enable device, error -22
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
janv. 28 14:39:49 pc-ses kernel: usb 1-4: reset high-speed USB device number 4 using xhci_hcd
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88003fae6048
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88003fae6000
janv. 28 14:39:49 pc-ses kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
janv. 28 14:39:49 pc-ses kernel: usb 1-2: hub failed to enable device, error -22
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
janv. 28 14:39:49 pc-ses kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
janv. 28 14:39:49 pc-ses kernel: usb 1-2: hub failed to enable device, error -22
janv. 28 14:39:49 pc-ses kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
janv. 28 14:39:49 pc-ses kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd

Comment 1 Milan Bouchet-Valat 2015-01-28 14:35:15 UTC
Created attachment 985199 [details]
xinput list

Comment 2 Hans de Goede 2015-01-28 15:03:43 UTC
This seems to be a duplicate of bug 1173849

Can you please try this update and see if it fixes thing ?  :

https://admin.fedoraproject.org/updates/FEDORA-2015-1008/gnome-settings-daemon-3.14.2-2.fc21

Comment 3 Milan Bouchet-Valat 2015-01-28 15:19:37 UTC
Indeed, the update fixes the problem. I can't believe I upgraded just a few days too early! :-)

*** This bug has been marked as a duplicate of bug 1173849 ***


Note You need to log in before you can comment on or make changes to this bug.