Bug 204179 - Mouse scroll stopped working after kernel upgrade from 5.1.16 -> 5.1.18
Summary: Mouse scroll stopped working after kernel upgrade from 5.1.16 -> 5.1.18
Status: NEW
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-14 17:53 UTC by Mikhail Morfikov
Modified: 2019-08-31 15:59 UTC (History)
6 users (show)

See Also:
Kernel Version: 5.1.18 5.2.0 5.2.1
Tree: Mainline
Regression: No


Attachments
lsusb (2.12 KB, text/plain)
2019-07-14 17:53 UTC, Mikhail Morfikov
Details

Description Mikhail Morfikov 2019-07-14 17:53:17 UTC
Created attachment 283689 [details]
lsusb

I have the following mouse:

$ lsusb
...
Bus 002 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / OP-620D

It was working well till the kernel 5.1.16. I upgraded the kernel to 5.1.18 and the mouse scroll doesn't work any more. The same issue is with the kernel 5.2.0 and 5.2.1 . I haven't tested it with the 5.1.17 version. 

When I compare the kernel .config file from 5.1.16 and 5.1.18, they're pretty much the same.
Comment 1 LukasH 2019-07-15 15:30:36 UTC
(In reply to Mikhail Morfikov from comment #0)
> Created attachment 283689 [details]
> lsusb
> 
> I have the following mouse:
> 
> $ lsusb
> ...
> Bus 002 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D /
> OP-620D
> 
> It was working well till the kernel 5.1.16. I upgraded the kernel to 5.1.18
> and the mouse scroll doesn't work any more. The same issue is with the
> kernel 5.2.0 and 5.2.1 . I haven't tested it with the 5.1.17 version. 
> 
> When I compare the kernel .config file from 5.1.16 and 5.1.18, they're
> pretty much the same.

I can confirm same issue. Fedora 30, 5.1.17-300.fc30.x86_64 kernel, the same mouse :

$ lsusb
...
Bus 003 Device 002: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D /OP-620D

First time I supposed that my mouse is gone, but then I rebooted into older 5.1.16 kernel - and everything works fine there.
Comment 2 LukasH 2019-07-17 14:22:24 UTC
I've been upgraded (F30) into the 5.1.18-300.fc30.x86_64 kernel before a while, problem still remains. So it has to be something (which occurs) between 5.1.16 and 5.1.17 and it's not solved yet.
Comment 3 Igor Kushnir 2019-07-17 18:26:17 UTC
Applying the following patch may fix this bug: https://www.spinics.net/lists/linux-input/msg61859.html.
See also https://bugzilla.kernel.org/show_bug.cgi?id=203369#c7.
Comment 4 LukasH 2019-07-18 15:19:31 UTC
Yes, this patch is working well, as I tested before a while and confirmed also in RedHat bugzilla there :

https://bugzilla.redhat.com/show_bug.cgi?id=1730762
Comment 5 Mikhail Morfikov 2019-07-18 17:42:32 UTC
I also can confirm the patch fixes the scroll issue (tested with the kernel 5.2.1).
Comment 6 dithpri 2019-07-18 22:55:09 UTC
I can also confirm the patch works, tested on kernel 5.2.0.
Comment 7 Ivan Kalvachev 2019-07-23 19:01:47 UTC
This patch fixes the scroll issue for me too.

I'm with fairly old A4Tech X6-005D 
a4tech 0003:09DA:000A.0001: input,hidraw0: USB HID v1.10 Mouse [A4Tech PS/2+USB Mouse]

I've tested it on 5.2.1 and 5.2.2.

I hope the patch will make it into 5.2.3.
Comment 8 LukasH 2019-07-28 10:09:17 UTC
Could anybody confirm, if this patch is (or isn't yet) included in the fresh 5.2.4 kernel, please ?
Comment 9 Igor Kushnir 2019-07-28 10:20:32 UTC
Probably not. You can search for "a4tech" in kernel patch change logs here: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.4 (replace the version number at the end of this URL to check out other versions).
Comment 10 LukasH 2019-07-28 16:25:13 UTC
Hmm, probably the same for 5.1.21 :-(. Is here somebody from upstream, who can say to us, when this patch is planned for (which) stable kernel? Or explain, why it will not be possible (in the near future) ? I understand, that sometimes the patch can have more cons than pros, can be dangerous/broken/whatever, but I guess this is not the case (as we already confirmed, inserting this patch into 5.1.18 kernel within Fedora kernel-tree works like a charm, nothing else is affected, etc.). Thanks.
Comment 11 Ivan Kalvachev 2019-07-31 01:41:48 UTC
This bug has been filled under Other/Other product/category, so it goes into "other" maillist. You can assume no developer would read that.

I opened a new bug into the correct category, but so far it seem to be ignored too.
https://bugzilla.kernel.org/show_bug.cgi?id=204347

I guess we need to escalate the things.
Comment 12 Ivan Kalvachev 2019-08-13 23:09:51 UTC
The patch has finally made it into linux-5.3-rc4

Maybe soon it will trickle down to older kernel patches.
Comment 13 Ivan Kalvachev 2019-08-31 15:59:04 UTC
The fix is in kernel 5.2.11 .

I don't think they would be releasing any more revisions of linux-5.1.x ,
so I consider the bug fixed.

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