All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Fri, 28 Mar 2008 06:34:33 -0500	[thread overview]
Message-ID: <1206704073.7112.51.camel@popeye> (raw)
In-Reply-To: <Pine.LNX.4.64.0803281223360.5541@jikos.suse.cz>

Juri - 

I think that you are correct - and have one - small - piece of subtle
evidence to support that position.  

While it has been a while since I have seen the repeating key issue,
from time to time I have noted that there is a lag of a few seconds
between the keyboard and the screen.

There is no way an old man lke myself is out-typeing his hardware.  This
is on a lightly loaded, dual core system with a few gig of memory.

Thanks

Chris


On Fri, 2008-03-28 at 12:24 +0100, Jiri Kosina wrote:
> On Fri, 28 Mar 2008, Chris Holvenstot wrote:
> 
> > I have not see the problem with "repeating keys" for a while now - since 
> > it was a "soft" failure I can not specify exactly which build was the 
> > last I saw it on.
> > I am currently running 2.6.25-rc7-git2
> > If you have questions abount the configuration of my kernel my config
> > file is attached.
> 
> Hi,
> 
> I think that this was one of the issues that were caused by 
> CONFIG_GROUP_SCHED, which were fixed a few weeks ago.
> 
> Still, the real issue is in Xorg, that their autorepeat code is very 
> unhappy when X process doesn't get scheduled often enough.
> 
> Thanks,
> 


  reply	other threads:[~2008-03-28 11:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 13:02 2.6.24-git15 Keyboard Issue? Chris Holvenstot
2008-02-06 13:23 ` Mark Hounschell
2008-02-06 13:28 ` Jiri Kosina
2008-02-06 13:49   ` Chris Holvenstot
2008-02-06 13:54     ` Jiri Kosina
2008-02-06 16:36       ` Kristoffer Ericson
2008-02-06 17:24       ` Chris Holvenstot
2008-02-07  9:18         ` Jiri Kosina
2008-02-07  9:51           ` Chris Holvenstot
2008-02-07 10:44           ` Chris Holvenstot
2008-02-07 10:51             ` Jiri Kosina
2008-02-07 12:29               ` Thomas Gleixner
2008-02-07 15:07                 ` Chris Holvenstot
2008-02-07 16:13                   ` Thomas Gleixner
2008-02-07 16:45                     ` Chris Holvenstot
2008-02-07 17:46                       ` Thomas Gleixner
2008-02-08  5:36                         ` Chris Holvenstot
2008-02-09  9:56                           ` Thomas Gleixner
2008-02-09 10:37                             ` Chris Holvenstot
2008-02-09 13:59                               ` Thomas Gleixner
2008-03-28 10:15                                 ` Thomas Gleixner
2008-03-28 11:20                                   ` Chris Holvenstot
2008-03-28 11:24                                     ` Jiri Kosina
2008-03-28 11:34                                       ` Chris Holvenstot [this message]
2008-02-08 15:08                         ` Jiri Kosina
2008-02-08 23:25                           ` Jiri Kosina

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=1206704073.7112.51.camel@popeye \
    --to=cholvenstot@comcast.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.