0461:4d51 Dell Laser Mouse stops working randomly

Bug #1019998 reported by Ken Sharp
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

While using my Dell Laser Mouse on my Precise system, it randomly stops working.

[17855.216119] usb 3-1: reset low-speed USB device number 2 using ohci_hcd
[17855.504148] usb 3-1: device descriptor read/64, error -62
[17855.896083] usb 3-1: device descriptor read/64, error -62
[17856.284472] usb 3-1: reset low-speed USB device number 2 using ohci_hcd
[17856.572175] usb 3-1: device descriptor read/64, error -62
[17856.964242] usb 3-1: device descriptor read/64, error -62
[17857.352067] usb 3-1: reset low-speed USB device number 2 using ohci_hcd
[17857.760256] usb 3-1: device not accepting address 2, error -62
[17858.044066] usb 3-1: reset low-speed USB device number 2 using ohci_hcd
[17858.452067] usb 3-1: device not accepting address 2, error -62
[17858.452164] usb 3-1: USB disconnect, device number 2
[17858.616290] usb 3-1: new low-speed USB device number 4 using ohci_hcd
[17858.756275] usb 3-1: device descriptor read/64, error -62
[17859.000284] usb 3-1: device descriptor read/64, error -62
[17859.240198] usb 3-1: new low-speed USB device number 5 using ohci_hcd
[17859.380068] usb 3-1: device descriptor read/64, error -62
[17859.624292] usb 3-1: device descriptor read/64, error -62
[17859.864259] usb 3-1: new low-speed USB device number 6 using ohci_hcd
[17860.272174] usb 3-1: device not accepting address 6, error -62
[17860.408214] usb 3-1: new low-speed USB device number 7 using ohci_hcd
[17860.816237] usb 3-1: device not accepting address 7, error -62
[17860.816272] hub 3-0:1.0: unable to enumerate USB device on port 1
[17890.232044] usb 3-1: new low-speed USB device number 8 using ohci_hcd

Unplugging it and plugging it back in brings it back.

[17890.410985] input: DELL Laser Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0/input/input14
[17890.411118] generic-usb 0003:0461:4D51.0004: input,hidraw0: USB HID v1.11 Mouse [DELL Laser Mouse] on usb-0000:00:12.0-1/input0

Everything works fine under Windows 7.

http://ubuntuforums.org/showthread.php?t=2011725

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-source (not installed)
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: fglrx wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC272X Analog [ALC272X Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ken 2833 F.... pulseaudio
 /dev/snd/controlC0: ken 2833 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xd2300000 irq 16'
   Mixer name : 'Realtek ALC272X'
   Components : 'HDA:10ec0272,1025036e,00100001'
   Controls : 20
   Simple ctrls : 11
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd2210000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Mon Jul 2 09:56:35 2012
HibernationDevice: RESUME=UUID=661410a7-5616-4cb0-a804-646cc87e86dd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Acer Aspire 5551
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=bcf30c65-9b6f-492c-896c-332ab1682c02 ro
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-26-generic N/A
 linux-backports-modules-3.2.0-26-generic N/A
 linux-firmware 1.79
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-06-26 (5 days ago)
dmi.bios.date: 07/27/2011
dmi.bios.vendor: Acer
dmi.bios.version: V2.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE50_DN
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.14
dmi.modalias: dmi:bvnAcer:bvrV2.14:bd07/27/2011:svnAcer:pnAspire5551:pvrV2.14:rvnAcer:rnJE50_DN:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.14:
dmi.product.name: Aspire 5551
dmi.product.version: V2.14
dmi.sys.vendor: Acer

Revision history for this message
Ken Sharp (kennybobs) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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 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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc5-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ken Sharp (kennybobs) wrote :

Yep, I will do. Bear in mind that this is a random problem so I'll have to run it for a while to determine if the bug exists upstream.

Revision history for this message
Ken Sharp (kennybobs) wrote :

I downloaded and installed the amd64 packages from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc5-quantal/ but the dkms modules for fglrx and bcmwl will not build. bcmwl I can do without for a while but not fglrx.

Looking at http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html the mainline kernel of the version I'm using is http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.19-precise/ which allows the dkms modules to build fine.

Do I definitely need to use the 3.5 kernel or will the 3.2 kernel be okay for testing?

Revision history for this message
Ken Sharp (kennybobs) wrote :

Okay so this bug still exists in the mainline 3.2 kernel mentioned above.

I cannot test the latest kernel, unless there is some way to get fglrx to build in dkms, but it has numerous build failures.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-unable-to-test-upstream
removed: needs-upstream-testing
Revision history for this message
Ken Sharp (kennybobs) wrote :

Not sure if this is helpful, given the environment it was running in, but under failsafe X with the 3.5 kernel then this bug still exists.

tags: added: kernel-bug-exists-upstream
removed: kernel-unable-to-test-upstream
penalvch (penalvch)
summary: - Dell Laser Mouse stops working randomly
+ 0461:4d51 Dell Laser Mouse stops working randomly
Revision history for this message
penalvch (penalvch) wrote :

Ken Sharp, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingMouseDetection#In_case_your_mouse_stops_working_after_a_while ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: hw-specific kernel-input
removed: dell hid mouse usb
Revision history for this message
Ken Sharp (kennybobs) wrote :

Just occurred again. Following a resume the mouse was working fine for a couple of minutes, then apparently powered off.

Remove/reinsert got it working again as before.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Ken Sharp, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1019998/comments/6 :
>'Not sure if this is helpful, given the environment it was running in, but under failsafe X with the 3.5 kernel then this bug still exists."

Which 3.5 kernel did you test specifically?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ken Sharp (kennybobs) wrote :

The amd64 kernel listed in comments 2 and 4.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.5-rc5-quantal needs-upstream-testing
removed: kernel-bug-exists-upstream
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Ken Sharp, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1019998/comments/10 :
>"The amd64 kernel listed in comments 2 and 4."

Thank you for clearing that up. Did this problem not occur in a release prior to Precise?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ken Sharp (kennybobs) wrote :

The problem occurred with a much greater frequency on Natty, which was the first Ubuntu I had on this laptop, and I skipped Oneiric.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Ken Sharp, thank you for providing the requested information. For regression testing purposes, could you please test for this problem in a Lucid live environment via http://releases.ubuntu.com/lucid/ ?

tags: added: natty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Heitor Moreira (heitormsilva) wrote :

I can confirm a very similar behaviour in my system. After upgrading from 12.04 to 12.10 I started to experiment some non random mouse freezes, in my case if I lift up the mouse from table and keep it for 2 seconds when I put it back on table it stops working (no cursor movement, no buttons response), even though the mouse remains powered (optical light remains on).

I've been using the same laptop and USB mouse for years without any problem and after this issue has started to bother me, I tested this same hardware in different Linux distributions without experimenting such problem.

When the mouse stop working, unplugging and re-plugging, makes it get back to work.

Revision history for this message
penalvch (penalvch) wrote :

Heitor, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

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
Revision history for this message
ryou ezoe (boostcpp) wrote :

This issue still persist in Ubuntu 13.04.

Revision history for this message
penalvch (penalvch) wrote :

ryou ezoe, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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