046d:c501 USB mouse does not get detected on bootup 25% of the time (USB bus reset)

Bug #686703 reported by b
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Every few days I turn on this AMD64 (A8V, 3200+) and the mouse does not move.
Even disconnecting and reconnecting the mouse does not work. I need to attach it to a different hub (front panel) for it to come up.

/var/log/messages shows 70 of the following messages during bootup:
Dec 7 09:54:56 insitu kernel: [ 24.210025] usb 3-2: reset low speed USB device using uhci_hcd and address 2

Then the following:
Dec 7 09:57:52 insitu kernel: [ 198.010552] usb 3-2: USB disconnect, address 2
Dec 7 09:57:52 insitu kernel: [ 198.131085] usb 3-2: new low speed USB device using uhci_hcd and address 3
Dec 7 09:58:23 insitu kernel: [ 228.820021] usb 3-2: new low speed USB device using uhci_hcd and address 4
Dec 7 09:58:53 insitu kernel: [ 259.400019] usb 3-2: new low speed USB device using uhci_hcd and address 5
Dec 7 09:59:24 insitu kernel: [ 289.980019] usb 3-2: new low speed USB device using uhci_hcd and address 6
Dec 7 09:59:34 insitu kernel: [ 300.520028] usb 3-2: new low speed USB device using uhci_hcd and address 7
Dec 7 09:59:48 insitu kernel: [ 313.910024] usb 3-2: new low speed USB device using uhci_hcd and address 8
Dec 7 10:00:18 insitu kernel: [ 344.510038] usb 3-2: new low speed USB device using uhci_hcd and address 9
Dec 7 10:00:49 insitu kernel: [ 375.100019] usb 3-2: new low speed USB device using uhci_hcd and address 10
Dec 7 10:00:59 insitu kernel: [ 385.650026] usb 3-2: new low speed USB device using uhci_hcd and address 11
Dec 7 10:03:34 insitu kernel: [ 539.710020] usb 3-1: new low speed USB device using uhci_hcd and address 12
Dec 7 10:04:04 insitu kernel: [ 570.310039] usb 3-1: new low speed USB device using uhci_hcd and address 13
Dec 7 10:04:48 insitu kernel: [ 613.910027] usb 5-1: new low speed USB device using uhci_hcd and address 2

I've marked this as a regression as I'm sure it was working in a previous version. I never had any problems with this mouse on ubuntu or debian. When the mouse works lsusb prints the following:

Bus 005 Device 002: ID 046d:c501 Logitech, Inc. Cordless Mouse Receiver

I also saw the following messages while the mouse was not working:

usb 3-2: device descriptor read/64, error -110
usb 3-2: device descriptor read/64, error -110
usb 3-2: device descriptor read/64, error -110
usb 3-2: device descriptor read/64, error -110
usb 3-2: device not accepting address 10, error -110
usb 3-2: device not accepting address 11, error -110

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bbogart 1335 F.... xfce4-volumed
                      bbogart 1347 F.... pulseaudio
 /dev/snd/controlC0: bbogart 1335 F.... xfce4-volumed
                      bbogart 1347 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8237'/'VIA 8237 with ALC850 at 0xe800, irq 22'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 49
   Simple ctrls : 30
Card1.Amixer.info:
 Card hw:1 'Bt878'/'Brooktree Bt878 at 0xdff00000, irq 19'
   Mixer name : 'Bt87x'
   Components : ''
   Controls : 3
   Simple ctrls : 5
Date: Tue Dec 7 10:35:07 2010
Frequency: Once every few days.
HibernationDevice: RESUME=UUID=13df1544-3ecd-4a0b-bea6-347f3f27871d
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-26-generic root=UUID=0ab4bde0-8376-4cbe-9bc0-af6c3a7936bd ro quiet splash
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:

SourcePackage: linux
WifiSyslog: Dec 7 10:39:00 insitu NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
dmi.bios.date: 08/16/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1018.002
dmi.board.name: A8V Deluxe
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1018.002:bd08/16/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
b (ben-ekran) wrote :
Revision history for this message
b (ben-ekran) wrote : Re: [Bug 686703] Re: USB mouse does not get detected on bootup 25% of the time (USB bus reset)

I just noticed some bus resets on my external USB drive.

Could this be a HW problem? What else can I do to debug?

On 10-12-07 11:03 AM, b wrote:
>
>

tags: added: regression-release
removed: regression-potential
Revision history for this message
Pierre-Antoine Champin (pchampin) wrote : Re: USB mouse does not get detected on bootup 25% of the time (USB bus reset)

I have a similar problem on a Dell Latitude E4310, and it appeared around the same period (december 2010): my USB cordless mouse stopped working intermittently, and plugin it out and back in does not always solve the problem.

I attach a fragment of /var/log/syslog where
at 09:29:06 I plug the USB receiver and the mouse works, and then
at 09:29:24 the mouse stops working, with a lot of USB errors in syslog.
later on, at 09:34:41, I plug the receiver again but it is not even recognized

Some info:

pa@nua:~$ lsusb
Bus 002 Device 035: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0461:4db1 Primax Electronics, Ltd
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pa@nua:~$ uname -a
Linux nua 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux

Revision history for this message
Pierre-Antoine Champin (pchampin) wrote :

Following my previous comment: this seems to be a hardware bug related to the USB receiver itself. Apparently, when I push it as far as possible into the USB plug, it goes *too* far and disconnects. If I pull it a little, it reconnects.

Still to be confirmed next time I reboot on Windows (may take a while ;-)

Revision history for this message
Pierre-Antoine Champin (pchampin) wrote :

I confirm that in my case, this was a hardware problem with the USB receiver (same problem under Windows).
Sorry for the noise.

Revision history for this message
b (ben-ekran) wrote : Re: [Bug 686703] Re: USB mouse does not get detected on bootup 25% of the time (USB bus reset)

I have not had the problem since using the PCI USB card.

Could be HW, or a kernel incompatibility with the a8V onboard USB.

Note I had a similar problem on my shuttle PC running debian. I'd get
weird bus resets with my arduino board. Everything was fine with the
same HW in windows, and using (the same) PCI USB card solved the problem.

Please let me know what I can do to seriously test this (other than
installing windows) as now I've got two 8+ USB port machines in which I
can only use 2 ports on a single PCI card I have to swap between them.

.b.

On 11-01-12 12:09 PM, Pierre-Antoine Champin wrote:
> I confirm that in my case, this was a hardware problem with the USB receiver (same problem under Windows).
> Sorry for the noise.
>

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Don Myers (donmyers) wrote : Re: USB mouse does not get detected on bootup 25% of the time (USB bus reset)

I've upgrade 8 computers from Ubuntu 10.10 to 11.04. Two of them have the issue of the USB mouse being frozen on boot, one 20% of the time, one 50% of the time. The keyboard works on both, although at least one is not using a USB keyboard . A restart does not work. A complete shutdown is necessary, plus crossed fingers, to get it to work. I discovered last night that generally unplugging the mouse and re-plugging in the mouse generally makes it work. Also, I have less problems if the mouse is plugged in the front USB ports than if it is plugged into the back USB ports. I've tried different mice, all of which worked fine under previous versions of Ubuntu 9.04, 9.10, 10.04, and 10.10. This is a new problem with 11.04. One computer is using nVidia graphics, and the other is using ATI, so it doesn't seem to be graphics related.

Revision history for this message
penalvch (penalvch) wrote :

b, 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/ .

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

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

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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

summary: - USB mouse does not get detected on bootup 25% of the time (USB bus
- reset)
+ 046d:c501 USB mouse does not get detected on bootup 25% of the time (USB
+ bus reset)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Don Myers (donmyers) wrote : Re: [Bug 686703] Re: 046d:c501 USB mouse does not get detected on bootup 25% of the time (USB bus reset)

I have not had any issues in Ubuntu 12.04. When it was an issue, a
generic mouse would not work but a Logitech mouse would work. Changing
the generic mouse to a front USB port would work, but using a rear port
would not work. If the mouse was frozen, simply unplugging it and
plugging it back in would allow it to work fine. Thinking about it, my
wife may have had an issue with her generic mouse in 12.04, but if she
did, I plugged it into a front USB port.

Don

On 07/25/2012 08:52 PM, Christopher M. Penalver wrote:
> b, 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/ .
>
> If it remains an issue, could you run the following command in the
> development release from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux <replace-with-bug-number>
>
> 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 . Please do
> not test the kernel in the daily folder, but the one all the way at the
> bottom. 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. As well, please comment
> on which kernel version specifically you tested.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> 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', and comment
> as to why specifically you were unable to test it.
>
> Please let us know your results. Thanks in advance.
>
> Helpful Bug Reporting Links:
> https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
> https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
> https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
> https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug
>
> ** Summary changed:
>
> - USB mouse does not get detected on bootup 25% of the time (USB bus reset)
> + 046d:c501 USB mouse does not get detected on bootup 25% of the time (USB bus reset)
>
> ** Attachment removed: "USB mouse works when plugged, then stops working"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/686703/+attachment/1790953/+files/syslog-usb-problem.txt
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

--

**

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.