Wireless mouse not working after boot

[Andrey Yurkovsky]

After OS boot wireless mouse not working. I've installed Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21. In logs:
kernel: [ 447.052149] usb 2-2: USB disconnect, address 2
kernel: [ 449.780047] usb 2-2: new low speed USB device using ohci_hcd and address 5
kernel: [ 450.007512] usb 2-2: configuration #1 chosen from 1 choice
kernel: [ 450.021448] input: Xhcms XHC Tec. as /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0/input/input7
kernel: [ 450.021642] generic-usb 0003:10CE:EB6C.0005: input,hidraw0: USB HID v1.10 Keyboard [Xhcms XHC Tec. ] on usb-0000:00:02.0-2/input0
kernel: [ 450.031759] generic-usb: probe of 0003:10CE:EB6C.0006 failed with error -22

When I replug mouse receiver it become working. In logs:
kernel: [ 538.540158] usb 2-2: USB disconnect, address 5
kernel: [ 546.630049] usb 2-8: new low speed USB device using ohci_hcd and address 6
kernel: [ 546.857385] usb 2-8: configuration #1 chosen from 1 choice
kernel: [ 546.867956] input: Xhcms XHC Tec. as /devices/pci0000:00/0000:00:02.0/usb2/2-8/2-8:1.0/input/input8
kernel: [ 546.868243] generic-usb 0003:10CE:EB6C.0007: input,hidraw0: USB HID v1.10 Keyboard [Xhcms XHC Tec. ] on usb-0000:00:02.0-8/input0
kernel: [ 546.883676] input: Xhcms XHC Tec. as /devices/pci0000:00/0000:00:02.0/usb2/2-8/2-8:1.1/input/input9
kernel: [ 546.884242] generic-usb 0003:10CE:EB6C.0008: input,hidraw3: USB HID v1.10 Mouse [Xhcms XHC Tec. ] on usb-0000:00:02.0-8/input1

Additionally information about device in attached files.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: anyr 1627 F.... pulseaudio
 /dev/snd/pcmC0D0p: anyr 1627 F...m pulseaudio
CRDA: Error: [Errno 2] Нет такого файла или каталога
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfecf4000 irq 23'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1695c601,00100002'
   Controls : 24
   Simple ctrls : 15
CheckboxSubmission: e4f59d9e0091afaf26aa0fa01bc5682c
CheckboxSystem: 4601f9caeefd0635ef3e8a58ac9462fd
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=da8545ca-8b01-4b95-8e93-a15f9ccc546f
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
Lsusb:
 Bus 002 Device 005: ID 10ce:eb6c Silicon Labs
 Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
 Bus 002 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-37-generic root=UUID=4fe839c5-cb5c-44e9-862a-9e494bf3ccbc ro quiet splash
ProcEnviron:
 LANGUAGE=ru_RU:ru:en
 LC_CTYPE=ru_RU.UTF-8
 LC_COLLATE=ru_RU.UTF-8
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21
Regression: No
RelatedPackageVersions: linux-firmware 1.34.13
Reproducible: Yes
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-37-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/27/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MCP61 DDR2: AF550G/Pro Series
dmi.board.vendor: EPoX COMPUTER CO., LTD
dmi.board.version: 1.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/27/2006:svn:pn:pvr:rvnEPoXCOMPUTERCO.,LTD:rnMCP61DDR2AF550G/ProSeries:rvr1.x:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 902811

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Andrey Yurkovsky (andrey.yurkovsky)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[penalvch (penalvch)]

Andrey Yurkovsky, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.