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/pci:00/: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-: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/pci:00/: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-: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/pci:00/: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-:00:1d.1-2/input0 [ 15.168021] input: Logitech USB Receiver as /devices/pci:00/: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-:00:1d.1-2/input1 [ 15.351289] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input8 [ 16.197368] usb 2-1.3: Manufacturer: Logitech [ 16.214741] input: Logitech USB Receiver as /devices/pci:00/: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-: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/pci:00/: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-: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/pci:00/: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-:00:1d.1-2/input0 [45776.192990] input: Logitech USB Receiver as /devices/pci:00/: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-: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/pci:00/: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-: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/pci:00/: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-: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
Bug#678215: [wheezy] USB mouse not recognized after resuming from suspend to RAM
Hi again, Jonathan Nieder wrote: Paul Menzel wrote: the mouse is not working after resuming from suspend to RAM. Replugging the mouse works although that is quite inconvenient. [...] - how does the 3.4.y kernel from experimental behave? - how does the 2.6.32.y kernel from stable behave? (It should work fine on a wheezy/sid system.) Beyond that, I have no great ideas, so if this is reproducible with 3.4.y, please send a summary of the symptoms to linux-...@vger.kernel.org, cc-ing either me or this bug log so we can track it. Be sure to mention Ping. Did you get a chance to try a newer or older kernel, and if so, what was the result? In suspense, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678215: [wheezy] USB mouse not recognized after resuming from suspend to RAM
Dear Jonathan, I am sorry for not reporting back on this issue. Am Montag, den 06.08.2012, 00:27 -0700 schrieb Jonathan Nieder: Jonathan Nieder wrote: Paul Menzel wrote: the mouse is not working after resuming from suspend to RAM. Replugging the mouse works although that is quite inconvenient. [...] - how does the 3.4.y kernel from experimental behave? - how does the 2.6.32.y kernel from stable behave? (It should work fine on a wheezy/sid system.) Beyond that, I have no great ideas, so if this is reproducible with 3.4.y, please send a summary of the symptoms to linux-...@vger.kernel.org, cc-ing either me or this bug log so we can track it. Be sure to mention Ping. Did you get a chance to try a newer or older kernel, and if so, what was the result? I contacted linux-...@vger.kernel.org [1][2] and it looks like that the mouse and the ASUS M2A-VM do not get along. Currently the motherboard is replaced by a different board ASRock A780Full HD and the USB mouse works without any problems with it. I am not certain if I am going to have the chance to test this again with the ASUS M2A-VM. So maybe we should just close this bug as (currently) unreproducible or moreinfo? Thanks, Paul [1] http://www.spinics.net/lists/linux-usb/msg65853.html [2] http://www.spinics.net/lists/linux-usb/msg65903.html signature.asc Description: This is a digitally signed message part
Bug#678215: [wheezy] USB mouse not recognized after resuming from suspend to RAM
retitle 678215 ASUS M2A-VM: USB mouse not recognized after resume from suspend to RAM forwarded 678215 http://thread.gmane.org/gmane.linux.usb.general/66109 tags 678215 = unreproducible quit Paul Menzel wrote: I am sorry for not reporting back on this issue. No problem. Thanks for the update. [...] I contacted linux-...@vger.kernel.org [1][2] and it looks like that the mouse and the ASUS M2A-VM do not get along. Currently the motherboard is replaced by a different board ASRock A780Full HD and the USB mouse works without any problems with it. Alan suggested that using a different mouse might work. Did you try that? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678215: [wheezy] USB mouse not recognized after resuming from suspend to RAM
reassign 678215 src:linux 3.2.20-1 quit Hi Paul, Paul Menzel wrote: after replacing a broken PS/2 mouse, which worked fine before that, with an USB mouse [...] Bus 003 Device 003: ID 1241:1122 Belkin Typhoon Stream Optical Mouse USB+PS/2 the mouse is not working after resuming from suspend to RAM. Replugging the mouse works although that is quite inconvenient. [...] I used that mouse on an ASUS EeePC 701 4G with outdated Debian Sid/unstable and Linux 3.0.0 without problems. Thanks for reporting it. I'd be curious to hear: - how does the 3.4.y kernel from experimental behave? - how does the 2.6.32.y kernel from stable behave? (It should work fine on a wheezy/sid system.) Beyond that, I have no great ideas, so if this is reproducible with 3.4.y, please send a summary of the symptoms to linux-...@vger.kernel.org, cc-ing either me or this bug log so we can track it. Be sure to mention - steps to reproduce, expected result, actual result, and how the difference indicates a bug - which kernel versions you have tested and what happened with each - full dmesg output from booting and reproducing the problem with an affected kernel - full lsusb -v output - any other weird symptoms or workarounds Hopefully someone upstream will have ideas for debugging this from there. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
