From: Joerg Sommrey <jo@sommrey.de>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: strange repeating keys and irq 0 routing on 2.6.x
Date: Tue, 8 Feb 2005 11:43:44 +0100 [thread overview]
Message-ID: <20050208104344.GA4229@sommrey.de> (raw)
Hi all,
a few times in the last couple of months I experienced some strange key
repeating in X. A single key-press sometimes results in 2-8 typed
keys. This started around 2.6.8 but I'm not sure. It was last seen on
2.6.10-ac8.
There were similar problems reported for Toshiba laptops and within XFree,
but my problem seems to be different.
The key repeating starts some hours after reboot and it gets
worse with time. After one day the keyboard is not usable anymore.
At the same time ntpd often fails reading the radio clock attached to a
serial port.
It doesn't happen after every reboot. BUT: Sometimes IRQ 0 is processed
on CPU1 after reboot (though /proc/irq/0/smp_affinity is 3 and all other
irq are handled on CPU0). In these cases the repeating keys appear.
The box has two Athlon MPs.
What can I do to gather more information?
-jo
--
-rw-r--r-- 1 jo users 63 2005-01-10 08:33 /home/jo/.signature
reply other threads:[~2005-02-08 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050208104344.GA4229@sommrey.de \
--to=jo@sommrey.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox