From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: 2.6.13-rc3 -> sluggish PS2 keyboard (was Re: [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01)
Date: Tue, 2 Aug 2005 10:55:27 -0500 [thread overview]
Message-ID: <d120d5000508020855797bed03@mail.gmail.com> (raw)
In-Reply-To: <1122997061.11253.3.camel@mindpipe>
On 8/2/05, Lee Revell <rlrevell@joe-job.com> wrote:
> On Tue, 2005-08-02 at 10:20 -0400, Steven Rostedt wrote:
> > On Tue, 2005-08-02 at 10:05 -0400, Lee Revell wrote:
> > > On Tue, 2005-08-02 at 09:56 -0400, Steven Rostedt wrote:
> > > > On Mon, 2005-08-01 at 00:45 -0400, Lee Revell wrote:
> > > > > On Sun, 2005-07-31 at 08:38 +0200, Ingo Molnar wrote:
> > > > > > ok - i've uploaded the -52-04 patch, does that fix it for you?
> > > > >
> > > > > Has anyone found their PS2 keyboard rather sluggish with this kernel?
> > > > > I'm not sure whether it's an -RT problem, I'll have to try rc4.
> > > >
> > > > I've just noticed this now. While I have lots of ssh sessions running,
> > > > my keyboard does get really sluggish. This hasn't happened before. I'm
> > > > currently running 2.6.13-rc3 with no RT. So this may definitely be a
> > > > mainline issue.
> > >
> > > I'm on a slower machine, and I seem to get this behavior regardless of
> > > load. Probably just running X+Gnome on this box is enough.
> > >
> > Also, I don't know if this is a kernel issue or a debian issue since I
> > updated my kernel at the same time I did a debian upgrade, and I'm using
> > debian unstable. Since debian unstable is going through some major
> > changes, this could be caused by that. I may be able to try some other
> > machines to see if they are affected, but that might take some time
> > before I can get to it.
> >
>
> Same here (s/debian/ubuntu/) but I have the exact same problem at the
> console, I don't think it could be an X issue unless X was able to wedge
> the keyboard controller.
>
> It feels like typing over a slow modem link, I can get about one word
> ahead of the cursor (X or console, regardless of load) but the delay
> seems to be constant.
>
Is this with ACPI? Have you tried playing with ec_polling parameter?
--
Dmitry
next prev parent reply other threads:[~2005-08-02 15:59 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 16:03 [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01 Ingo Molnar
2005-07-30 20:47 ` Peter Zijlstra
2005-07-30 20:52 ` Ingo Molnar
2005-07-31 4:47 ` Lee Revell
2005-07-31 6:38 ` Ingo Molnar
2005-08-01 4:45 ` Lee Revell
2005-08-01 21:08 ` Ingo Molnar
2005-08-01 21:12 ` Ingo Molnar
2005-08-02 13:56 ` Steven Rostedt
2005-08-02 14:05 ` Lee Revell
2005-08-02 14:20 ` Steven Rostedt
2005-08-02 15:37 ` 2.6.13-rc3 -> sluggish PS2 keyboard (was Re: [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01) Lee Revell
2005-08-02 15:44 ` Vojtech Pavlik
2005-08-02 15:46 ` Lee Revell
2005-08-02 15:47 ` Lee Revell
2005-08-02 15:53 ` Steven Rostedt
2005-08-02 15:55 ` Vojtech Pavlik
2005-08-02 15:55 ` Dmitry Torokhov [this message]
2005-08-02 15:38 ` [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01 Lee Revell
2005-07-31 8:03 ` Peter Zijlstra
2005-07-31 10:44 ` Ingo Molnar
2005-07-31 15:56 ` [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-05 Gene Heskett
2005-08-01 18:22 ` [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01 Steven Rostedt
2005-08-01 19:49 ` Steven Rostedt
2005-08-01 20:52 ` Ingo Molnar
2005-08-01 21:09 ` Daniel Walker
2005-08-01 21:15 ` Ingo Molnar
2005-08-02 0:43 ` Steven Rostedt
2005-08-01 21:15 ` Steven Rostedt
2005-08-01 21:23 ` Ingo Molnar
2005-08-01 21:20 ` Daniel Walker
2005-08-02 0:53 ` Steven Rostedt
2005-08-02 10:19 ` Ingo Molnar
2005-08-02 19:45 ` Steven Rostedt
2005-08-02 19:56 ` Steven Rostedt
2005-08-02 23:38 ` Daniel Walker
2005-08-03 0:00 ` Steven Rostedt
2005-08-03 1:12 ` George Anzinger
2005-08-03 1:48 ` Keith Owens
2005-08-03 2:12 ` George Anzinger
2005-08-03 2:25 ` Daniel Walker
2005-08-03 2:42 ` Steven Rostedt
2005-08-03 2:58 ` Daniel Walker
2005-08-03 10:30 ` Steven Rostedt
2005-08-03 15:10 ` Daniel Walker
2005-08-03 10:37 ` [Question] arch-independent way to differentiate between user and kernel Steven Rostedt
2005-08-03 10:48 ` Ingo Molnar
2005-08-03 12:18 ` Steven Rostedt
2005-08-03 10:56 ` [Question] arch-independent way to differentiate between user andkernel linux-os (Dick Johnson)
2005-08-03 11:44 ` Steven Rostedt
2005-08-03 12:04 ` Ingo Molnar
2005-08-03 12:30 ` Steven Rostedt
2005-08-03 14:50 ` [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.52-01 Steven Rostedt
2005-08-03 15:15 ` Steven Rostedt
2005-08-03 15:57 ` Steven Rostedt
2005-08-03 16:44 ` Steven Rostedt
[not found] ` <20050812125844.GA13357@elte.hu>
2005-08-26 4:24 ` Steven Rostedt
2005-08-26 6:08 ` Ingo Molnar
2005-08-26 11:20 ` Steven Rostedt
2005-08-30 10:58 ` Stephen C. Tweedie
2005-08-30 11:14 ` Ingo Molnar
2005-08-30 11:00 ` Stephen C. Tweedie
2005-08-02 3:55 ` Steven Rostedt
2005-08-02 4:07 ` Daniel Walker
2005-08-02 14:53 ` Steven Rostedt
2005-08-04 12:20 ` Andrzej Nowak
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=d120d5000508020855797bed03@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.org \
--cc=vojtech@suse.cz \
/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