From: Danny Brow <dan@fullmotions.com>
To: Kernel-List <linux-kernel@vger.kernel.org>
Subject: Sluggish typing
Date: Mon, 09 Jan 2006 04:18:57 -0500 [thread overview]
Message-ID: <1136798337.30826.9.camel@localhost> (raw)
After trying numerous kernel versions I've had very sluggish typing in
the console since 2.6.13-rcX (can't remember when it started). But I
have to hit a key twice, cursor up or down does not show history, some
times it does nothing, other times it acts like I hit tab-tab. I'm
running 2.6.15 on 4 system, 2.6.15-rc2 on my laptop and they all have
this problem. I have 2 servers right now with the same problem, I think
they are 2.6.14.2. All custom configs. All the systems are intel
p4/pd/centrino, various chipsets, i845, i875p, i925. Is their a patch or
work around for this problem. I have spoke with a few other people with
the same problem.
Also sometimes it stops and all is fine for about 10 seconds, irq
polling issue?
Please help,
TIA,
Dan.
ps. please cc as I'm not subscribed to the list.
next reply other threads:[~2006-01-09 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 9:18 Danny Brow [this message]
2006-01-09 15:13 ` Sluggish typing Dmitry Torokhov
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=1136798337.30826.9.camel@localhost \
--to=dan@fullmotions.com \
--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