All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	elendil@planet.nl, Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>,
	Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.25-rc1] jerky mouse cursor and randoooom key repeats
Date: Tue, 26 Feb 2008 09:37:36 -0600	[thread overview]
Message-ID: <1204040256.12792.58.camel@popeye> (raw)
In-Reply-To: <Pine.LNX.4.64.0802261602030.30955@jikos.suse.cz>

Jiri - 

For what it is worth, and understand that it is hard to prove a
negitive, on slack moments over the weekend I repeatedly booted my
system into single user (console) mode using a kernel with
CONFIG_GROUP_SCHED set to yes.

To date I have NOT been able to recreate the repeating key issue outside
of X.

Chris


On Tue, 2008-02-26 at 16:05 +0100, Jiri Kosina wrote:
> On Tue, 26 Feb 2008, Lennart Sorensen wrote:
> 
> > Hmm, I have been seeing repeated keys a lot under X on my athlon 700, 
> > but mainly when I have firefox running (which is of course quite a load 
> > on the poor old thing).  This has been going on for probably the last 
> > year or so.  I thought it was just the machine getting weird, although 
> > whenever it wasn't running firefox or other memory/cpu heavy loads it 
> > seemed fine.
> 
> This could be caused by the fact that as far as I know, X are not using 
> kernel-autorepeat, but they are handling it themselves, right? So if their 
> sense of time (probably due to some change of kernel timekeeping) gets 
> wrong, the autorepeat in X might also get wrong.
> 
> It would be nice to know if when you hit the situation when autorepeat 
> goes strange in X, if it is still OK in console.
> 


  reply	other threads:[~2008-02-26 15:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16  0:53 [2.6.25-rc1] jerky mouse cursor and randoooom key repeats Chris Holvenstot
2008-02-16 11:03 ` Jiri Kosina
2008-02-16 11:18   ` Chris Holvenstot
2008-02-16 12:05   ` Chris Holvenstot
2008-02-16 18:08     ` Jiri Kosina
2008-02-16 18:54       ` Chris Holvenstot
2008-02-17  4:09       ` Chris Holvenstot
2008-02-21  9:37         ` Jiri Kosina
2008-02-21  9:45           ` Chris Holvenstot
2008-02-26 14:58             ` Lennart Sorensen
2008-02-26 15:05               ` Jiri Kosina
2008-02-26 15:37                 ` Chris Holvenstot [this message]
2008-02-26 21:58                 ` Lennart Sorensen
2008-02-26 22:01                   ` Jiri Kosina
2008-02-26 22:04                     ` Lennart Sorensen
2008-02-27  0:08                       ` Nigel Cunningham
  -- strict thread matches above, loose matches on Subject: below --
2008-02-11 15:23 [2.6.25-rc0 System no longer powers off after shutdown Frans Pop
2008-02-13  8:41 ` [2.6.25-rc1] jerky mouse cursor and randoooom key repeats Frans Pop
2008-02-15 23:58   ` Pavel Machek
2008-02-16  1:23     ` Gabriel C
2008-02-16  6:19       ` Mike Galbraith
2008-02-16 10:09         ` Gabriel C
2008-02-16 14:03           ` Mike Galbraith

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=1204040256.12792.58.camel@popeye \
    --to=cholvenstot@comcast.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=elendil@planet.nl \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=mingo@elte.hu \
    /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.