LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Wed, 06 Feb 2008 07:49:00 -0600	[thread overview]
Message-ID: <1202305740.9058.22.camel@popeye> (raw)
In-Reply-To: <Pine.LNX.4.64.0802061427410.30873@twin.jikos.cz>

Thank you for your response, Jiri - 


On this system I am using a PS2 Keyboard - and let me stress that it is
only occasionaly that it happens - I have had 2.6.24-git15 up for about
2 hours now and have only seen it about a dozen times.

I also note one other thing - although my system is lightly loaded - at
this time of day I am pretty much just using email on an AMD 64 X2 4600+
with 2 gigs of of memory - I have noticed several times that I will be
typing away and nothing is appearing on the screen - and a few seconds
later - boom - there it all is.

There is no way an old fella like me should be able to out type a system
like this.

Chris



On Wed, 2008-02-06 at 14:28 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
> 
> > I built 2.6.24-git15 this morning and seem to have picked up a little 
> > "funny" along the way - occasionally what should be a single key stroke 
> > ends up spraying multiple characters on to my screen. By this I mean I 
> > type "w" and get "wwwwwwwww" or whatever. This has happened a number of 
> > times with random keys so I don't think that it is a sticky key and I 
> > did not see this on previous builds.
> 
> What keyboard is that? (USB/PS2?).
> 


  reply	other threads:[~2008-02-06 13:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 13:02 Chris Holvenstot
2008-02-06 13:23 ` Mark Hounschell
2008-02-06 13:28 ` Jiri Kosina
2008-02-06 13:49   ` Chris Holvenstot [this message]
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
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=1202305740.9058.22.camel@popeye \
    --to=cholvenstot@comcast.net \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.24-git15 Keyboard Issue?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).