I'm not sure whether it gives any information, but here is some output
from journalctl, where the bug happens (no "clocksource=jiffies" boot
option is used):
$ journalctl -k | grep clocksource
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 7645519600211568 ns
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
clocksource: Switched to clocksource refined-jiffies
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2879c5f06f2,
max_idle_ns: 440795220049 ns
clocksource: Switched to clocksource tsc
clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as
unstable because the skew is too large:
clocksource: 'refined-jiffies' wd_now: fffedcd0 wd_last:
fffedc58 mask: ffffffff
clocksource: 'tsc' cs_now: 13ccf176fe cs_last: 13299ba17d
kernel: tsc: Marking TSC unstable due to clocksource watchdog
kernel: clocksource: Switched to clocksource refined-jiffies
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Keyboard keys get stuck and repeat
Status in GNU Emacs:
Status in Linux:
Status in X.Org X server:
Status in linux package in Ubuntu:
Status in xorg-server package in Ubuntu:
Status in linux source package in Jaunty:
Status in xorg-server source package in Jaunty:
Status in Gentoo Linux:
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/~desktop-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp