Bug#690162: mouse/keyboard stop working after s2ram until hid_logitech reloaded

[Jonathan Nieder <jrnieder@gmail.com>]

retitle 690162 [3.4->3.5.5 regression] mouse/keyboard stop working after s2ram until hid_logitech reloaded
# regression
severity 690162 important
quit

Hi Michael,

Michael Schmitt wrote:

> [Subject: 3.5-trunk-686-pae]

Please keep in mind that these appear as emails in a crowded inbox, so
the subject line can be a good place to put valuable context.

[...]
> 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

Thanks.  Ideas:

 - Can you reproduce this from the console, without X running?

 - How do you suspend?  "echo mem >/sys/power/state" is a good way to
   make the process as simple for people interpreting what happened as
   possible.

 - Please attach full "dmesg" output from booting, suspending, and
   then unloading and reloading the hid_logitech module on a working
   and non-working kernel.

 - What was the first non-working kernel?  If you have time to bisect
   through the pre-compiled kernels at
   http://snapshot.debian.org/package/linux/ to find the oldest broken
   and newest non-broken one, that would be very useful.

Hope that helps,
Jonathan