I'm sorry for flooding this thread, but I have more experience to share.

After another reboot in "clocksource=jiffies" mode, I saw that 1 OS
second passes in real 0.5 seconds. But the rest of the system was pretty
stable. Keyboard auto-repeat was twice as fast, but did not get
triggered inadvertently.

I did another reboot in "clocksource=jiffies" mode and opened the online clock 
application. Initially the clock speed seemed normal. After 20-30 seconds it 
became twice as fast.
Then from the console, I started an application with an infinite loop therein. 
That made the clock seconds turn very very fast. Probably CPU speed has 
influence here.

Good news is that when I changed the boot option to "clocksource=tsc", I
got stable results even after a few reboots. Seconds seem to pass as
fast as they should be.

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

  Keyboard keys get stuck and repeat

Status in GNU Emacs:
Status in Linux:
Status in X.Org X server:
  In Progress
Status in linux package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in xorg-server source package in Jaunty:
Status in Gentoo Linux:

Bug description:
  Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
  get 'stuck' and continue being 'clicked' even after they are
  physically released. For example when clicking Alt-F4, sometimes it
  gets stuck so all the windows are closed instead of just one.

  My configuration is Feisty + Xgl + Compiz Fusion. My previous
  configuration was Edgy + Xgl + Beryl, where this didn't happen. Others
  have reported the same problem without using either Xgl or Compiz.

  The keyboard itself isn't the problem. When dual-booting to Windows,
  everything works fine. Also, the problem happens with two different
  keyboards (internal laptop, external USB).

  My best guess is that the problem occurs at time of high system load.
  Somehow during these times the key-release signal gets lost and the
  key-press is repeated indefinitely. This happens more often with
  Compiz configurations because Compiz tends to increase system load. It
  also happens more often with power-hungry apps like Firefox and
  Acrobat Reader for similar reasons.

  PS: When the keys would repeat all input devices would be locked up.
  ie. mouse won't move, clicks don't do anything, keyboard presses don't
  register. Then when it becomes unstuck, the mouse moves around and
  everything. Hope this helps.

  See also this forum thread for other people with the same problem:

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to