[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#690162: marked as done ([3.4->3.5.5 regression] mouse/keyboard stop working after s2ram until hid_logitech reloaded)

Your message dated Fri, 23 Apr 2021 16:18:28 +0200
with message-id <YILXNPd8yBcz5m7l@eldamar.lan>
and subject line Re: Bug#690162: 3.5-trunk-686-pae
has caused the Debian Bug report #690162,
regarding [3.4->3.5.5 regression] mouse/keyboard stop working after s2ram until hid_logitech reloaded
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
690162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690162
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 3.5.5-1~experimental.1
Severity: normal

Dear maintainers,
after resume from s2ram my mouse from a Logitech mouse/keyboard-set does not work anymore. Reloading hid_logitech.ko fixes the mouse again. Keyboard works always. The former version off linux-image-3.5 from experimental was affected too, sids 3.4 did not have that issue.
Device: Bus 002 Device 007: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser 

Mainboard: Asus P5LD2-SE

See attached:
dmesg_3.4-trunk-686-pae_bootup.txt
- Kernel 3.4, cold-boot, all working

dmesg_3.4-trunk-686-pae_s2ram+resume_working.txt
- Kernel 3.4, s2ram and resume, all working

dmesg_3.5-trunk-686-pae_bootup.txt
- Kernel 3.5, cold-boot, all working

dmesg_3.5-trunk-686-pae_s2ram+resume_broken.txt
- Kernel 3.5, s2ram and resume, mouse not working

dmesg_3.5-trunk-686-pae_s2ram+resume_modprobe_working.txt
- Kernel 3.5, s2ram and resume, mouse working after modprobe-cycle
At timestamp [ 165.450234] in "dmesg_3.5-trunk-686-pae_s2ram+resume_modprobe_working.txt" (essentially the same file as "*broken*txt", just with a modprobe-cycle at the end) I see 

usbhid 2-1.3:1.1: >reset_resume error 1

which is not present in the testrun with kernel 3.4.

If you need anymore information, just ask.

regards and greetings
Michael
P.S.: I do have a second (currently not used) Logitech-USB-receiver connected, kinda hard to reach the connector to unplug it, if you wonder why dmesg shows a second receiver...
--- End Message ---
--- Begin Message --- 
Hi

Assuming the issue is not anymore reproducible on recent kernels I'm 
going to close this bugreport by now to clean up the list of src:linux
bugs from very old issues. In case you can reproduce the issue feel
free to reopen the bug.
 
Regards,
Salvatore

--- End Message ---
Reply to: