usb mouse not working after resume from Suspend to RAM

[Tim Lunn]

I am running Jaunty on my Thinkpad R52.

usb mouse does not work after resuming from suspend to RAM. the only way I can get it work again is to unplug it and plug it back in.

I did have a similar issue in a previous version and was able to resolve it by reloading the "ehci_hcd and uhci_hcd" modules. however these now seem to be built into the kernel ?

have tried reloading usbhid but that does not help either.

[nelliott (nelliott-gci)]

I am experiencing the exact symptoms on my HP DV9207us. Just like Tim, I was previously able to prevent this problem by unloading uhci_hcd before suspend via /etc/pm/config.d/config. This no longer works with Jaunty. The only solution I have at this time is to disconnect/reconnect the USB mouse.

[Chow Loong Jin (hyperair)]

On Mon, 2009-06-15 at 04:43 +0000, nelliott wrote:
> I am experiencing the exact symptoms on my HP DV9207us. Just like Tim,
> I was previously able to prevent this problem by unloading uhci_hcd
> before suspend via /etc/pm/config.d/config. This no longer works with
> Jaunty. The only solution I have at this time is to
> disconnect/reconnect the USB mouse.
>
Try usbhid. I think that's what it's called now, though I may be
mistaken.
--
Regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Contributing Developer

[Tim Lunn (darkxst)]

I had tried that previously, it does not help.

On 06/15/2009 03:01 PM, Chow Loong Jin wrote:
> On Mon, 2009-06-15 at 04:43 +0000, nelliott wrote:
>
>> I am experiencing the exact symptoms on my HP DV9207us. Just like Tim,
>> I was previously able to prevent this problem by unloading uhci_hcd
>> before suspend via /etc/pm/config.d/config. This no longer works with
>> Jaunty. The only solution I have at this time is to
>> disconnect/reconnect the USB mouse.
>>
>>
> Try usbhid. I think that's what it's called now, though I may be
> mistaken.
>

[nelliott (nelliott-gci)]

Sorry, should have mentioned that I tried usbhid as well, without success.

[Richard Appleby (disposable01)]

I saw this exact same problem under Jaunty, and worse, continue to see this problem under Karmic Alpha 6 too. Logitech wireless mouse, not recognised after resume from RAM on a Thinkpad T60p. Unloading/loading uhci_hcd doesn't seem to work. Worse, under Karmic, neither does unplugging and replugging the mouse. Problem isn't 100% reproducible either. Happens maybe 50% of the time. Mouse is always detected as a usb device however; see output from lsusb:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 010: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 005 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 011: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

$ sudo lsusb -s 0004:011 -vv

Bus 004 Device 011: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x046d Logitech, Inc.
  idProduct 0xc501 Cordless Mouse Receiver
  bcdDevice 9.10
  iManufacturer 1 Logitech
  iProduct 2 USB Receiver
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 34
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 50mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 1 Boot Interface Subclass
      bInterfaceProtocol 2 Mouse
      iInterface 0
      ** UNRECOGNIZED: 09 21 10 01 00 01 22 52 00
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 10
Device Status: 0x0000
  (Bus Powered)

$ uname -a
Linux t60p 2.6.31-10-generic #34-Ubuntu SMP Wed Sep 16 00:23:19 UTC 2009 i686 GNU/Linux

[Tim Lunn (darkxst)]

Just tested suspend to RAM on my latop using alpha 6 live CD.

my usb mouse works fine after resume.

On 23/09/09 15:32, SixedUp wrote:
> I saw this exact same problem under Jaunty, and worse, continue to see
> this problem under Karmic Alpha 6 too. Logitech wireless mouse, not
> recognised after resume from RAM on a Thinkpad T60p. Unloading/loading
> uhci_hcd doesn't seem to work. Worse, under Karmic, neither does
> unplugging and replugging the mouse. Problem isn't 100% reproducible
> either. Happens maybe 50% of the time. Mouse is always detected as a usb
> device however; see output from lsusb:
>
> $ lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 005 Device 010: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
> Bus 005 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 011: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> $ sudo lsusb -s 0004:011 -vv
>
> Bus 004 Device 011: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 1.10
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 8
> idVendor 0x046d Logitech, Inc.
> idProduct 0xc501 Cordless Mouse Receiver
> bcdDevice 9.10
> iManufacturer 1 Logitech
> iProduct 2 USB Receiver
> iSerial 0
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 34
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xa0
> (Bus Powered)
> Remote Wakeup
> MaxPower 50mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 1
> bInterfaceClass 3 Human Interface Device
> bInterfaceSubClass 1 Boot Interface Subclass
> bInterfaceProtocol 2 Mouse
> iInterface 0
> ** UNRECOGNIZED: 09 21 10 01 00 01 22 52 00
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0008 1x 8 bytes
> bInterval 10
> Device Status: 0x0000
> (Bus Powered)
>
> $ uname -a
> Linux t60p 2.6.31-10-generic #34-Ubuntu SMP Wed Sep 16 00:23:19 UTC 2009 i686 GNU/Linux
>
>

[Tim Lunn (darkxst)]

have now upgaded my laptop to Karmic Beta,

mouse seems to be working fine after suspend to RAM..

Although have bigger issues now in the form of Kernel Ooops after resume, but thats for another bug report I guess.

[Richard Appleby (disposable01)]

Agreed, it's working fine on Karmic Alpha 6 upgraded with the latest fixes. I guess this can be closed now.

[Ernst (ernst-blaauw)]

Well, I just resumed after a suspend in an up to date Karmic. I cannot get my mouse to work,. Unplugging and replugging does not solve it.

$ apt-cache policy pm-utils
pm-utils:
  Installed: 1.2.5-2ubuntu7
  Candidate: 1.2.5-2ubuntu7
  Version table:
 *** 1.2.5-2ubuntu7 0
        500 http://nl.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

[Jeremy Foshee (jeremyfoshee)]

Hi Tim,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 368268

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Tim Lunn (darkxst)]

This issue was resolved in Karmic. I no longer have the affected computer either, so wont be able to further test it in Lucid.

[Ernst (ernst-blaauw)]

At the moment, I cannot reproduce this in Lucid. I guess it is solved for
me.

On Sun, Mar 14, 2010 at 21:42, Tim <email address hidden> wrote:

> This issue was resolved in Karmic. I no longer have the affected
> computer either, so wont be able to further test it in Lucid.
>
> --
> usb mouse not working after resume from Suspend to RAM
> https://bugs.launchpad.net/bugs/368268
> You received this bug notification because you are a direct subscriber
> of the bug.
>