kernel-packages team mailing list archive

Thread
Date
[Bug 627862] Re: USB Mouse freezes randomly but consistently

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: "Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>
Date: Tue, 20 Aug 2013 09:41:59 -0000
Reply-to: Bug 627862 <627862@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
PhilX, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

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

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

Thank you for your understanding.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/627862

Title:
  USB Mouse freezes randomly but consistently

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Mouse (USB) freezes during X session at random intervals (between 1min
  and 5 hours apart). Only known workaround is to reboot when it
  happens.

  Mouse only freezes when being used, if the computer is unattended, no
  freezing will occur.

  It has occurred in Ubuntu 9.10 and now 10.04 (i believe 9.04 was OK).
  Ive running the latest updates in the 10.04 build.

  I can continue to use the system via the keyboard (USB). I have found
  that if two mice are connected before one locks up, the second will
  continue to work for a time, but is still susceptible to the above.

  Once the mouse stops working, replugging into alternate USB ports or
  the same does not fix it.

  Ive scanned the following logs after the event and I find no useful info:
  * /var/log/Xorg.0.log
  * /var/log/messages
  * /var/log/daemon.log

  The kernel log does not have any info immediately after the event, but after around two minutes, the following appears:
  --------
  Sep  1 15:37:06 quantum kernel: [89521.010037] INFO: task khubd:44 blocked for more than 120 seconds.
  Sep  1 15:37:06 quantum kernel: [89521.010044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Sep  1 15:37:06 quantum kernel: [89521.010049] khubd         D ffffffff81a26a38     0    44      2 0x00000000
  Sep  1 15:37:06 quantum kernel: [89521.010059]  ffff8800790c7bb0 0000000000000046 0000000000015bc0 0000000000015bc0
  Sep  1 15:37:06 quantum kernel: [89521.010067]  ffff8800790c9ab0 ffff8800790c7fd8 0000000000015bc0 ffff8800790c96f0
  Sep  1 15:37:06 quantum kernel: [89521.010073]  0000000000015bc0 ffff8800790c7fd8 0000000000015bc0 ffff8800790c9ab0
  Sep  1 15:37:06 quantum kernel: [89521.010080] Call Trace:
  Sep  1 15:37:06 quantum kernel: [89521.010094]  [<ffffffff813d7915>] usb_kill_urb+0x85/0xc0
  Sep  1 15:37:06 quantum kernel: [89521.010104]  [<ffffffff81085430>] ? autoremove_wake_function+0x0/0x40
  Sep  1 15:37:06 quantum kernel: [89521.010110]  [<ffffffff813d7bab>] ? usb_get_urb+0x1b/0x30
  Sep  1 15:37:06 quantum kernel: [89521.010116]  [<ffffffff813d6233>] usb_hcd_flush_endpoint+0x133/0x140
  Sep  1 15:37:06 quantum kernel: [89521.010122]  [<ffffffff813d858d>] usb_disable_endpoint+0x5d/0x90
  Sep  1 15:37:06 quantum kernel: [89521.010127]  [<ffffffff813d8609>] usb_disable_device+0x49/0x130
  Sep  1 15:37:06 quantum kernel: [89521.010134]  [<ffffffff813d2402>] usb_disconnect+0xd2/0x170
  Sep  1 15:37:06 quantum kernel: [89521.010141]  [<ffffffff813d2a6f>] hub_port_connect_change+0x8f/0x980
  Sep  1 15:37:06 quantum kernel: [89521.010147]  [<ffffffff813d3d62>] hub_events+0x3b2/0x5a0
  Sep  1 15:37:06 quantum kernel: [89521.010154]  [<ffffffff81541d70>] ? thread_return+0x48/0x418
  Sep  1 15:37:06 quantum kernel: [89521.010161]  [<ffffffff813d3fa5>] hub_thread+0x55/0x190
  Sep  1 15:37:06 quantum kernel: [89521.010167]  [<ffffffff81085430>] ? autoremove_wake_function+0x0/0x40
  Sep  1 15:37:06 quantum kernel: [89521.010173]  [<ffffffff813d3f50>] ? hub_thread+0x0/0x190
  Sep  1 15:37:06 quantum kernel: [89521.010178]  [<ffffffff810850b6>] kthread+0x96/0xa0
  Sep  1 15:37:06 quantum kernel: [89521.010184]  [<ffffffff810141ea>] child_rip+0xa/0x20
  Sep  1 15:37:06 quantum kernel: [89521.010189]  [<ffffffff81085020>] ? kthread+0x0/0xa0
  Sep  1 15:37:06 quantum kernel: [89521.010194]  [<ffffffff810141e0>] ? child_rip+0x0/0x20
  ------

  After the event, running 'lsusb' will block and not return anything
  indefinitely.

  Which has lead me to believe its a kernel related thing?

  Im technically minded, so if you need anything else let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-24-generic 2.6.32-24.42
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  x          1899 F.... pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfe020000 irq 20'
     Mixer name	: 'Nvidia MCP78 HDMI'
     Components	: 'HDA:10ec0888,10438321,00100101 HDA:10de0002,10de0101,00100000'
     Controls      : 44
     Simple ctrls  : 23
  Date: Wed Sep  1 16:08:37 2010
  EcryptfsInUse: Yes
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=8c10f5d0-c0de-4bdc-a1b4-41fe260fc70d
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
   
   eth1      no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=40ac7fe5-d476-4d60-b2c4-a5836c4069dc ro splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.utf8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: linux-firmware 1.34.1
  RfKill:
   
  SourcePackage: linux
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M3N78 PRO ACPI BIOS Revision 0203
  dmi.board.name: M3N78 PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N78PROACPIBIOSRevision0203:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78PRO:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/627862/+subscriptions