Re: Linux 3.2: USB mouse not recognized after resuming from suspend to RAM

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

 



Am Mittwoch, den 20.06.2012, 17:34 +0200 schrieb Paul Menzel:
> Am Mittwoch, den 20.06.2012, 11:11 -0400 schrieb Alan Stern:
> > On Wed, 20 Jun 2012, Paul Menzel wrote:
> > 
> > > [This message is more a less the same as sent to the Debian BTS
> > > <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678215>.]
> 
> > > after replacing a broken PS/2 mouse, which worked fine before that, with
> > > an USB mouse
> > > 
> > >         $ lsusb # output from after the resume and replugged
> > >         Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > >         Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > >         Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > >         Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > >         Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > >         Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > >         Bus 002 Device 004: ID 046d:c30f Logitech, Inc. Logicool HID-Compliant Keyboard (106 key)
> > >         Bus 002 Device 003: ID 058f:9254 Alcor Micro Corp. Hub
> > >         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.
> > 
> > ...
> > >         [    1.660039] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
> > >         [    1.660042] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> > >         [    3.108025] usb 3-1: new low-speed USB device number 2 using ohci_hcd
> > >         [    3.273061] usb 3-1: New USB device found, idVendor=1241, idProduct=1122
> > >         [    3.273066] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > >         [    3.282359] input: HID 1241:1122 as /devices/pci0000:00/0000:00:13.1/usb3/3-1/3-1:1.0/input/input2
> > >         [    3.282472] generic-usb 0003:1241:1122.0003: input,hidraw2: USB HID v1.00 Mouse [HID 1241:1122] on usb-0000:00:13.1-1/input0
> > > 
> > > Now the system is resuming after `sudo pm-suspend`.
> > > 
> > >         [12498.968042] usb 2-2: reset full-speed USB device number 3 using ohci_hcd
> > >         [12512.152050] usb 2-1: USB disconnect, device number 2
> > >         [12512.544068] usb 3-1: USB disconnect, device number 2
> > > 
> > > Could the above disconnect be the problem here?
> > 
> > Undoubtedly it is related.
> > 
> > >         [12512.968046] usb 2-1: new low-speed USB device number 4 using ohci_hcd
> > >         [12513.143894] usb 2-1: New USB device found, idVendor=046d, idProduct=c30f
> > >         [12513.143901] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> > >         [12513.143905] usb 2-1: Product: Logitech USB Keyboard
> > >         [12513.143908] usb 2-1: Manufacturer: Logitech
> > >         [12513.157357] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.0/input/input5
> > >         [12513.157747] generic-usb 0003:046D:C30F.0004: input,hidraw0: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:13.0-1/input0
> > >         [12513.170016] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.1/input/input6
> > >         [12513.170314] generic-usb 0003:046D:C30F.0005: input,hidraw1: USB HID v1.10 Device [Logitech Logitech USB Keyboard] on usb-0000:00:13.0-1/input1
> > > 
> > > The keyboard is detected twice, but not the mouse.
> > > 
> > >         [12710.284049] usb 3-2: new low-speed USB device number 3 using ohci_hcd
> > >         [12710.449087] usb 3-2: New USB device found, idVendor=1241, idProduct=1122
> > >         [12710.449097] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > >         [12710.458732] input: HID 1241:1122 as /devices/pci0000:00/0000:00:13.1/usb3/3-2/3-2:1.0/input/input7
> > >         [12710.459106] generic-usb 0003:1241:1122.0006: input,hidraw2: USB HID v1.00 Mouse [HID 1241:1122] on usb-0000:00:13.1-2/input0
> > > 
> > > Replugging the mouse makes it work again. So the mouse is not recognized
> > > after the resume.
> > > 
> > > Switching the USB port does not make any difference either.
> > > 
> > > I used that mouse on an ASUS EeePC 701 4G with outdated Debian
> > > Sid/unstable and Linux 3.0.0 without problems.
> > 
> > Evidently the mouse doesn't like the computer.  Have you tried using a 
> > different mouse?
> 
> No, I do not have another USB mouse here. The PS/2 one worked fine.

I found another USB mouse and this worked without problems.

> > > Another problem indicating the board ASUS M2A-VM [1] behaves strangely,
> > > is that the USB keyboard also randomly stops working. When I switched
> > > the USB ports today I even got something in the Linux kernel ring
> > > buffer.
> > > 
> > >         $ dmesg | grep EMI
> > >         [ 2454.450355] hub 4-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
> > 
> > If that happens only when you move the cable between ports, you don't 
> > need to worry about it.  It should never happen while the cable is 
> > plugged in normally.
> 
> So I need to worry. :/ That message is only related the Logitech
> keyboard I have here and it happened right during operation. No cables
> were taken out. After plugging it out and in the keyboard worked again.
> 
> > > Although it is weird again, that this happened on the other port too but
> > > I only found this one message with `zgrep EMI /var/log/syslog*`. A post
> > > on LinuxQuestions.org suggests this is due to bad shielding of the USB
> > > cable. But I did not have these problems with the same keyboard on the
> > > ASUS EeePC 701 4G.
> > 
> > The bad shielding could be in the port, or where the port connects to 
> > the cable, or where the port connects to the motherboard.  It doesn't 
> > have to be in the cable or the mouse.
> 
> As written I got this EMI message only with the *keyboard* one time
> today.
> 
> > > Any hints on how to solve this issue are very much appreciated.
> > 
> > The cheapest and easiest solution is to replace the mouse.
> 
> True. I still would like to figure out what is going on. It is very
> strange that the mouse issue only happens during resume, on every USB
> port and is reproducible.
> 
> I guess I need to recompile the Linux kernel with `CONFIG_USB_DEBUG`
> set.

Alright, I have a different motherboard now (ASRock A780FullHD) and the
mouse works fine with it.


Thanks for all your help,

Paul

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux