Bug#678215: [wheezy] USB mouse not recognized after resuming from suspend to, RAM
Hi folks,
I have the exact same symptom here with Linux kernel 3.5-trunk from
experimental. AFAIR kernel 3.4 did fine, but I will retest that if required.
mschmitt@adrastea:~$ dmesg |egrep -i "hid|logitech|input"
[ 0.694199] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[ 1.165742] usbcore: registered new interface driver usbhid
[ 1.165745] usbhid: USB HID core driver
[ 1.769359] usb 2-2: Manufacturer: Logitech
[ 2.309359] usb 2-1.3: Manufacturer: Logitech
[ 2.326683] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.3/2-1.3:1.0/input/input1
[ 2.326733] logitech 0003:046D:C517.0003: input,hidraw0: USB HID
v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-1.3/input0
[ 2.358395] logitech 0003:046D:C517.0004: fixing up Logitech keyboard
report descriptor
[ 2.359049] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.3/2-1.3:1.1/input/input2
[ 2.359159] logitech 0003:046D:C517.0004: input,hiddev0,hidraw1: USB
HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-1.3/input1
[ 12.856786] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
[ 12.856851] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[ 13.166321] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 15.117371] usb 2-2: Manufacturer: Logitech
[ 15.134701] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input6
[ 15.134778] hid-generic 0003:046D:C505.0005: input,hidraw0: USB HID
v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-2/input0
[ 15.168021] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.1/input/input7
[ 15.168168] hid-generic 0003:046D:C505.0006: input,hidraw1: USB HID
v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-2/input1
[ 15.351289] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input8
[ 16.197368] usb 2-1.3: Manufacturer: Logitech
[ 16.214741] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.3/2-1.3:1.0/input/input9
[ 16.214857] logitech 0003:046D:C517.0007: input,hidraw2: USB HID
v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-1.3/input0
[ 16.246404] logitech 0003:046D:C517.0008: fixing up Logitech keyboard
report descriptor
[ 16.247307] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.3/2-1.3:1.1/input/input10
[ 16.247505] logitech 0003:046D:C517.0008: input,hiddev0,hidraw3: USB
HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-1.3/input1
[ 32.281185] input: ACPI Virtual Keyboard Device as
/devices/virtual/input/input11
[45720.066279] usbhid 2-1.3:1.1: reset_resume error 1
[45728.331269] input input6: event field not found
[45728.331271] input input6: event field not found
[45728.331273] input input6: event field not found
[45728.331275] input input6: event field not found
[45728.331277] input input6: event field not found
[45728.331279] input input6: event field not found
[45728.331291] input input6: event field not found
[45728.331301] input input7: event field not found
[45728.331303] input input7: event field not found
[45728.331304] input input7: event field not found
[45728.331305] input input7: event field not found
[45728.331306] input input7: event field not found
[45728.331308] input input7: event field not found
[45728.331309] input input7: event field not found
[45775.992026] usbcore: deregistering interface driver usbhid
[45776.162500] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input12
[45776.162688] hid-generic 0003:046D:C505.0009: input,hidraw0: USB HID
v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-2/input0
[45776.192990] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.1/input/input13
[45776.193745] hid-generic 0003:046D:C505.000A: input,hidraw1: USB HID
v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-2/input1
[45776.235573] usbcore: registered new interface driver usbhid
[45776.235576] usbhid: USB HID core driver
[45776.244126] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.3/2-1.3:1.0/input/input14
[45776.246070] logitech 0003:046D:C517.000B: input,hidraw2: USB HID
v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-1.3/input0
[45776.246082] logitech 0003:046D:C517.000C: fixing up Logitech keyboard
report descriptor
[45776.246719] input: Logitech USB Receiver as
/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.3/2-1.3:1.1/input/input15
[45776.250968] logitech 0003:046D:C517.000C: input,hiddev0,hidraw3: USB
HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-1.3/input1
That is a boot / suspend / resume cycle and see "[45720.066279] usbhid
2-1.3:1.1: reset_resume error 1" and the "event field not found" lines
The hardware is "Bus 002 Device 007: ID 046d:c517 Logitech, Inc. LX710
Cordless Desktop Laser" so at least same vendor and I guess the same
kernel-module as the original reporter. Reloading hid_logitech.ko fixes
the issue too (see the last few lines in the log above). In my case it
is a mouse / keyboard set connected wireless to the same receiver.
Right now I do not have any other usb-mouse around to test, but I assume
only Logitech or at least some Logitech mice are affected. Keyboard
works reliably after resume (as said, same receiver).
I have a Asus P5LD2-SE as Mainboard here, same vendor as the M2A-VM from
the original reporter. Here it is an Intel ICH7 chipset, I doubt the
M2A-VM (AMD?) has the same....
No idea if the issue is really the same (the log snippets do look
different) but I really doubt it that the mainboard is the general issue
here (as said, worked on anything before kernel 3.5). Could be a
coincidence and two genuine issues, but somehow I doubt that at least
right now. If others feel differently there, I will report a new bug for
sure.
Oh, almost forgotten, I run sid and not wheezy. :)
regards
Michael
P.S.: a sidenote, I have another Logitech usb receiver connected. As the
connector is very inconviniently placed on the back-side of the computer
(hard to get there in my setup) it just uses power and has no associated
mouse or keyboard connected. Just FYI if you wonder why the logs may
show another receiver...
Reply to: