aptosid.com

Hardware - Logitech mouse won't resume after suspend

pumrel - 09.09.2012, 09:32
Post subject: Logitech mouse won't resume after suspend
Hi,
I have a cordless Logitech kit ex110. When I resume from suspend the mouse pointer doesn't move. The keyboard resumes alright.

I think it is not kernel related as it does with every kernel I have. It appeared after one upgrade when udev was upgraded so it might be the culprit but nevertheless I still don't know how to debug.

I saved dmesg and lsusb after resuming.

dmesg
      Code:

[16900.560026] usb 1-5: new high-speed USB device number 3 using ehci_hcd
[16900.677835] usb 1-5: New USB device found, idVendor=04a9, idProduct=267e
[16900.677840] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[16900.677843] usb 1-5: Product: Canon CAPT USB Device
[16900.677846] usb 1-5: Manufacturer: Canon
[16900.677848] usb 1-5: SerialNumber: 00001166UG54
[17012.666173] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[17047.430025] usb 1-5: reset high-speed USB device number 3 using ehci_hcd
[17279.872023] usb 1-5: reset high-speed USB device number 3 using ehci_hcd
[17364.583314] usb 1-5: USB disconnect, device number 3
[27735.878206] PM: Syncing filesystems ... done.
[27736.200777] Freezing user space processes ... (elapsed 0.01 seconds) done.
[27736.212100] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[27736.223124] Suspending console(s) (use no_console_suspend to debug)
[27736.223519] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[27736.223614] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[27736.223703] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[27736.226310] sd 0:0:0:0: [sda] Stopping disk
[27736.226359] sd 1:0:0:0: [sdb] Stopping disk
[27736.226402] sd 2:0:0:0: [sdc] Stopping disk
[27736.226467] i8042 kbd 00:0c: wake-up capability enabled by ACPI
[27736.226782] serial 00:0a: disabled
[27736.226786] serial 00:0a: wake-up capability disabled by ACPI
[27736.228048] ACPI handle has no context!
[27736.327098] ACPI handle has no context!
[27736.329126] ACPI handle has no context!
[27736.786042] PM: suspend of devices complete after 562.659 msecs
[27736.786250] PM: late suspend of devices complete after 0.206 msecs
[27736.797121] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
[27736.808079] uhci_hcd 0000:00:1d.2: wake-up capability enabled by ACPI
[27736.808117] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
[27736.808154] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
[27736.808188] ehci_hcd 0000:00:1a.7: wake-up capability enabled by ACPI
[27736.819057] uhci_hcd 0000:00:1a.2: wake-up capability enabled by ACPI
[27736.819094] uhci_hcd 0000:00:1a.1: wake-up capability enabled by ACPI
[27736.819131] uhci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI
[27736.819168] PM: noirq suspend of devices complete after 32.916 msecs
[27736.819573] ACPI: Preparing to enter system sleep state S3
[27736.819766] PM: Saving platform NVS memory
[27736.820310] Disabling non-boot CPUs ...
[27736.821534] CPU 1 is now offline
[27736.822055] Extended CMOS year: 2000
[27736.822055] ACPI: Low-level resume complete
[27736.822055] PM: Restoring platform NVS memory
[27736.822055] Extended CMOS year: 2000
[27736.822055] Enabling non-boot CPUs ...
[27736.824249] Booting Node 0 Processor 1 APIC 0x1
[27736.838075] CPU1 is up
[27736.839844] ACPI: Waking up from system sleep state S3
[27736.840169] uhci_hcd 0000:00:1a.0: wake-up capability disabled by ACPI
[27736.840205] uhci_hcd 0000:00:1a.1: wake-up capability disabled by ACPI
[27736.840240] uhci_hcd 0000:00:1a.2: wake-up capability disabled by ACPI
[27736.840277] ehci_hcd 0000:00:1a.7: wake-up capability disabled by ACPI
[27736.840419] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
[27736.840454] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
[27736.840489] uhci_hcd 0000:00:1d.2: wake-up capability disabled by ACPI
[27736.840526] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
[27736.840898] PM: noirq resume of devices complete after 0.848 msecs
[27736.840972] PM: early resume of devices complete after 0.047 msecs
[27736.841000] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[27736.841023] usb usb3: root hub lost power or was reset
[27736.841036] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[27736.841055] usb usb4: root hub lost power or was reset
[27736.841066] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[27736.841085] usb usb5: root hub lost power or was reset
[27736.841097] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[27736.841148] snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
[27736.841198] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[27736.841201] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[27736.841220] usb usb6: root hub lost power or was reset
[27736.841223] usb usb7: root hub lost power or was reset
[27736.841234] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[27736.841238] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[27736.841255] usb usb8: root hub lost power or was reset
[27736.841256] pci 0000:00:1e.0: setting latency timer to 64
[27736.841267] ata_piix 0000:00:1f.2: setting latency timer to 64
[27736.841271] ata_piix 0000:00:1f.5: setting latency timer to 64
[27736.841337] snd_hda_intel 0000:01:00.1: irq 45 for MSI/MSI-X
[27736.844265] atl1 0000:02:00.0: irq 46 for MSI/MSI-X
[27736.844316] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[27736.846820] serial 00:0a: activated
[27736.846829] i8042 kbd 00:0c: wake-up capability disabled by ACPI
[27736.850335] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[27736.850385] radeon 0000:01:00.0: WB enabled
[27736.850387] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000010000c00 and cpu addr 0xffff8801a59e9c00
[27736.881613] [drm] ring test on 0 succeeded in 1 usecs
[27736.881628] [drm] ib test on ring 0 succeeded in 0 usecs
[27737.159652] ata4: SATA link down (SStatus 0 SControl 300)
[27737.306024] usb 6-1: reset low-speed USB device number 2 using uhci_hcd
[27737.396043] firewire_core 0000:04:03.0: rediscovered device fw0
[27737.836038] usb 4-1: reset low-speed USB device number 2 using uhci_hcd
[27738.172462] usbhid 4-1:1.1: reset_resume error 1
[27742.346068] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[27742.346077] ata1.01: SATA link down (SStatus 0 SControl 300)
[27742.348013] ata3: link is slow to respond, please be patient (ready=0)
[27742.365156] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[27742.365159] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[27742.365264] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[27742.365266] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[27742.404251] ata1.00: configured for UDMA/133
[27742.404391] sd 0:0:0:0: [sda] Starting disk
[27742.656018] ata2.00: link is slow to respond, please be patient (ready=0)
[27743.011146] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[27743.014140] ata3.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[27743.014143] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[27743.014547] ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[27743.014549] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[27743.041386] ata3.00: configured for UDMA/133
[27743.041415] sd 2:0:0:0: [sdc] Starting disk
[27746.175082] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[27746.175092] ata2.01: SATA link down (SStatus 0 SControl 300)
[27746.178133] ata2.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[27746.178135] ata2.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[27746.178508] ata2.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[27746.178511] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[27746.185136] ata2.00: configured for UDMA/133
[27746.185558] sd 1:0:0:0: [sdb] Starting disk
[27749.192057]
[27749.192058] floppy driver state
[27749.192059] -------------------
[27749.192078] now=4322416488 last interrupt=4294667825 diff=27748663 last called handler=reset_interrupt [floppy]
[27749.192079] timeout_message=lock fdc
[27749.192079] last output bytes:
[27749.192081]  8 80 4294667810
[27749.192082]  8 90 4294667810
[27749.192082]  8 80 4294667811
[27749.192083]  8 80 4294667823
[27749.192084]  8 90 4294667823
[27749.192085]  8 90 4294667823
[27749.192086]  8 90 4294667823
[27749.192086]  e 80 4294667824
[27749.192087] 13 80 4294667824
[27749.192088]  0 90 4294667824
[27749.192089] 1a 90 4294667824
[27749.192090]  0 90 4294667824
[27749.192090] 12 90 4294667824
[27749.192091]  0 90 4294667824
[27749.192092] 14 90 4294667824
[27749.192093] 18 90 4294667824
[27749.192094]  8 80 4294667825
[27749.192094]  8 80 4294667825
[27749.192095]  8 80 4294667825
[27749.192096]  8 80 4294667825
[27749.192097] last result at 4294667825
[27749.192098] last redo_fd_request at 4294667825
[27749.192103] status=2
[27749.192104] fdc_busy=1
[27749.192107] do_floppy=reset_interrupt [floppy]
[27749.192108] cont=ffffffffa005f970
[27749.192109] current_req=          (null)
[27749.192109] command_status=-1
[27749.192110]
[27749.192113] floppy0: floppy timeout called
[27749.192318] PM: resume of devices complete after 12351.343 msecs
[27749.192557] Restarting tasks ... done.

pumrel - 09.09.2012, 09:33
Post subject:
lsusb
      Code:

Bus 004 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 006 Device 002: ID 056a:0060 Wacom Co., Ltd Volito
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

OppaErich - 02.10.2012, 08:09
Post subject:
Ah, I'm not alone. I have this too since about 3 weeks. A Logitech wireless desktop, the keyboard works, the mouse does not. Have to pull the USB plug and push it back in to revive the mouse.
piper - 02.10.2012, 17:23
Post subject:
In system settings > input devices > mouse

do you have extra settings like "cordless mx duo reciever" or something along those lines, if you do, maybe it can help using a different channel, just a suggestion at best and might (probably) not do jack squat
All times are GMT - 12 Hours
Powered by PNphpBB2 © 2003-2010 The Zafenio Group
Credits