Red Hat Bugzilla – Bug 152546
key sticking on davej's test kernel
Last modified: 2015-01-04 17:18:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
upon booting the kernel, keys randomly seem to "stick" (that is, they repeat, although i've already let them go), resulting in typing that looks like "thiiiiiiiiiis". occurs often enough to happen every few sentences.
also, the system seems generally jerky/sluggish.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot kernel.
2. type something.
*** Bug 152547 has been marked as a duplicate of this bug. ***
Have you confirmed that it goes back to normal with the previous kernel?
There is nothing we can do about this report if you don't give more details
about your hardware. Also please ATTACH the following output gotten immediately
after a reboot:
Created attachment 112463 [details]
Created attachment 112464 [details]
Created attachment 112465 [details]
right. i accidentally did an upgrade instead of an install (force of habit) so
all my other kernels are gone for the time being. i'll download the latest
stable one to make sure, but i'm relatively sure it's the problem.
ok i went back to the latest stable kernel. it's fine.
as i'm booting the test kernel, i notice sluggishness as early as before the
initscripts start running. I've got quiet disabled, and i notice even those
kernel messages come out more slowly.
still a problem with kernel kernel-smp-2.6.11-1.9_FC3.
do i need to give more info ?
I highly suggest searching upstream lkml mailing list or google for anything
similar, and maybe posting there for help. This is a very odd report, I have
personally never heard anything like it. If you find anything related please
provide URLs here.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.