Bug 208923

Summary:	mouse not respond with kernel 5.9rc1
Product:	Drivers	Reporter:	denisdens (denisdens57)
Component:	Input Devices	Assignee:	drivers_input-devices
Status:	RESOLVED CODE_FIX
Severity:	high	CC:	1i5t5.duncan, denisdens57
Priority:	P1
Hardware:	Intel
OS:	Linux
Kernel Version:	5.9 RC2	Subsystem:
Regression:	Yes	Bisected commit-id:
Attachments:	revert d31327922 usbhid: do not sleep when opening device patch

Description denisdens 2020-08-16 22:51:14 UTC

Mouse logitech m220 not respond  ! 

gigabyte brix blcd5005 


downgrade at kernel 5.8 and ok ....

Comment 1 Duncan 2020-08-17 07:07:49 UTC

Created attachment 290949 [details]
revert d31327922 usbhid: do not sleep when opening device patch

Do you build your own kernel and can you patch or git-revert?

If so, try reverting d3132792285859253c466354fd8d54d1fe0ba786, or applying the attached patch.

I'm filing a bug on my issue ATM, but if you can confirm the revert/patch works for you I'll dupe it to this one, since I've confirmed reverting that (via the patch) works for my bug.  Bug # 208935 FWIW.

Comment 2 Duncan 2020-08-18 09:38:22 UTC

(In reply to Duncan from comment #1)
> Created attachment 290949 [details]
> revert d31327922 usbhid: do not sleep when opening device patch

Someone confirmed on my bug #208935 that reverting that commit gave him a working mouse again, and he and I both use pointing devices with a wireless Unified receiver, which googling (on the more privacy respecting duckduckgo) the m220 you have suggests you use as well, so it probably is a dupe.  But as you've not responded yet I can't confirm it so will ask you to resolve/duplicate to mine, if/when you do confirm.  Either way, but that bug now has more information and confirmation.

Comment 3 denisdens 2020-08-18 22:21:11 UTC

hello ! thanks for your response mr Duncan (i m french ,my english is very old lol sorry ) ...

i run with kernel installed with ubuntu mainline kernel installer (same ukuu but FREE !!! ) .. 

for the moment not have a time(hard and lot of work with car)  for study this problem...

for me down for the moment at 5.8 ....new test with RC2 ...rc3 

if find a time i long test ,observe and study this   


other signal same problem (bug#208935) =confirmed 

thanks at community and thanks

Comment 4 denisdens 2020-08-18 22:21:28 UTC

at You

Comment 5 denisdens 2020-08-24 02:10:41 UTC

same problem with 5.9RC2 ....

Comment 6 Duncan 2020-08-27 07:48:20 UTC

Bug #208935 is fixed by reverting the problem commit in mainline now, so hopefully when rc3's out to test this one's resolved too. =:^)

Comment 7 denisdens 2020-08-27 23:53:51 UTC

(In reply to Duncan from comment #6)
> Bug #208935 is fixed by reverting the problem commit in mainline now, so
> hopefully when rc3's out to test this one's resolved too. =:^)

Hello ! Thanks ! :D ;) ok awaiting rc3 ....Thanks ! i publishing return here test rc3
 thanks at You ! and a community

Comment 8 denisdens 2020-08-31 21:49:49 UTC

yes !!!!
 resolved in RC3 ! Thanks Mr Duncan 
and a all community ,high like for You ! ;)  

// resolved //