← Back to team overview

kernel-packages team mailing list archive

[Bug 1062114] Re: usb behaving strangely (e.g. abrupt mouse movements, usb keyboard loosing key events)


Martin Vysny, this bug report is being closed due to your last comment
regarding this being fixed with a BIOS update. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: linux (Ubuntu)
       Status: Incomplete => Invalid

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  usb behaving strangely (e.g. abrupt mouse movements, usb keyboard
  loosing key events)

Status in “linux” package in Ubuntu:

Bug description:
  After some boots, the USB mouse behaves strangely (abrupt mouse movements), also, USB keyboard tends to loose some keypresses. This behavior occurs randomly (I can't find out what's causing this) and lasts from the point when lightdm is displayed until the computer is rebooted. This issue never starts to manifest during computer runtime - either it is present right from the Ubuntu start, or it does not occur. The issue is never present in grub menu, in Windows, nor in BIOS menu. Sometimes, the bug manifests in multiple consecutive reboots.
  Running commands as described here: http://davidjb.com/blog/2012/06/restartreset-usb-in-ubuntu-12-04-without-rebooting fixes the issue (until the following computer boot - not necessarily the very next boot). There is an interesting warning in my dmesg about ignored IRQ 17 - perhaps it is somehow related?

  [   40.224653] irq 17: nobody cared (try booting with the "irqpoll" option)
  [   40.224668]  [<c10c6d49>] __report_bad_irq+0x29/0xd0
  [   40.224678]  [<c10c4e3f>] handle_irq_event_percpu+0x9f/0x1d0
  [   40.224680]  [<c10c7970>] ? unmask_irq+0x30/0x30
  [   40.224688]  [<c10c4fab>] handle_irq_event+0x3b/0x60
  [   40.224689]  [<c10c7970>] ? unmask_irq+0x30/0x30
  [   40.224691]  [<c10c79be>] handle_fasteoi_irq+0x4e/0xd0
  [   40.224692]  <IRQ>  [<c15cff12>] ? do_IRQ+0x42/0xc0
  [   40.224728] [<c142feb0>] usb_hcd_irq
  [   40.224729] Disabling IRQ #17

  I'm running Quantal x86-32 on Dell Latitude E6510, but the problem
  manifested also on 12.04, 11.10 and perhaps other versions as well.
  Please see the files attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-16-generic 3.5.0-16.25
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic i686
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
   /dev/snd/controlC0:  vyzivus    2491 F.... pulseaudio
  Date: Fri Oct  5 10:40:58 2012
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=526ee35e-1401-4a70-837e-003755e37121
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: Dell Inc. Latitude E6510
   Socket 0:
     no product info available
   Socket 0:
     no card
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=02dfb985-99c1-431d-882f-87475db02062 ro splash elevator=noop vt.handoff=7
   linux-restricted-modules-3.5.0-16-generic N/A
   linux-backports-modules-3.5.0-16-generic  N/A
   linux-firmware                            1.94
  SourcePackage: linux
  UpgradeStatus: Upgraded to quantal on 2012-10-03 (1 days ago)
  dmi.bios.date: 11/20/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 02K3Y4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to: