You are not logged in.

#1 2014-12-27 04:37:01

Los Frijoles
Member
Registered: 2012-06-23
Posts: 38

XInput pointing devices become floating slaves after resume

I got an Asus X200M laptop back around May and I have been running arch on it since the start. One problem that has cropped up in the past few months has been that every once in a while, the touchscreen or trackpad (or both) will stop sending input to X after the computer resumes from a suspend. Until this week, I had simply restarted the machine to fix the problem (a solution I despised).

The thing that changed this past week is that I suddenly was unable to use a Logitech USB mouse after plugging it in. My movements of the mouse had no effect. I googled around and found out about the xinput command and using it I discovered that for some reason the mouse was a "floating slave" and wasn't attached to the virtual pointer which caused it to appear to not work. At that point I used the xinput command to manually attach it and all was well. Then, the next time my mice stopped working after a resume I ran the xinput command and got the following:

[508]kcuzner@kcuzner-netbook:~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[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)]
∼ USBest Technology SiS HID Touch Controller	id=10	[floating slave]
∼ Logitech Unifying Device. Wireless PID:1025	id=11	[floating slave]
∼ ETPS/2 Elantech Touchpad                	id=14	[floating slave]

I was extremely surprised! Something had made all of my mice become floating slaves! I looked at my log and discovered the following lines right after I resumed the machine:

Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-2: hub failed to enable device, error -22
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-2: hub failed to enable device, error -22
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fca5180
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fca51c8
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4: reset high-speed USB device number 3 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4: hub failed to enable device, error -22
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4: reset high-speed USB device number 3 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4: hub failed to enable device, error -22
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4: reset high-speed USB device number 3 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fc61900
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4.2: reset full-speed USB device number 4 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4.2: hub failed to enable device, error -22
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4.2: reset full-speed USB device number 4 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4.2: hub failed to enable device, error -22
Dec 26 20:46:30 kcuzner-netbook kernel: usb 1-4.2: reset full-speed USB device number 4 using xhci_hcd
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fe71180
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fe712a0
Dec 26 20:46:30 kcuzner-netbook kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fe71300
Dec 26 20:46:30 kcuzner-netbook kernel: PM: resume of devices complete after 1696.129 msecs
Dec 26 20:46:30 kcuzner-netbook kernel: PM: Finishing wakeup.

I don't know if these are the culprit of my issue, but it doesn't seem out of the question. Reattaching all of the pointers to the virtual core pointer fixed the problem of the mice not working.

My questions are these:

- What is causing my devices to become floating when I resume?

- How can I prevent this from occurring? It's extremely annoying.

I've attempted to search for this problem, but half the issue is that I don't know what to search. I end up getting results like the xinput manual and people trying to disable their mouses and such.

Last edited by Los Frijoles (2014-12-27 04:37:53)

Offline

Board footer

Powered by FluxBB