Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1686056
| From | Olof Johansson <olof@lixom.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Regression during 4.13 merge window: Mouse not working (under X) |
| Date | 2017-07-12 23:50 +0200 |
| Message-ID | <u2xGa-59T-11@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Dmitry, I installed current mainline (as of 3b06b1a744) on a z840 here, and lost the mouse. Bisecting down, it seems like "HID: usbhid: remove custom locking from usbhid_open/close" (e399396a6b0) is at fault, and if I revert that and 283a21da1239 I get a working system again. Userspace is Ubuntu 16.04. Looking at X and dmesg logs, the only delta I see is that in the _good_ case I have a couple of these in dmesg: usb 3-12: Device not responding to setup address. usb 3-12: Device not responding to setup address. 3-12 unrelated to keyboard/mouse though (it's a 4-port hub, likely internal to the PC), so seems like a red herring. So, not sure just what's the root cause here, but allowing concurrent opens seems to make for unhappiness. It's a pretty small patch and nothing in it seems wrong, besides the change in behavior on allowing concurrent opens (removal of the mutex). -Olof
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Regression during 4.13 merge window: Mouse not working (under X) Olof Johansson <olof@lixom.net> - 2017-07-12 23:50 +0200
Re: Regression during 4.13 merge window: Mouse not working (under X) Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2017-07-13 00:00 +0200
Re: Regression during 4.13 merge window: Mouse not working (under X) Olof Johansson <olof@lixom.net> - 2017-07-13 02:10 +0200
csiph-web