public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jan Knutar <jk-lkml@sci.fi>,
	linux-kernel@vger.kernel.org, Hans-Peter Jansen <hpj@urpla.net>,
	David Newall <davidn@davidnewall.com>,
	Theodore Tso <tytso@mit.edu>, "Fred ." <eldmannen@gmail.com>
Subject: Re: Keys get stuck
Date: Thu, 13 Mar 2008 13:02:01 +0100	[thread overview]
Message-ID: <1205409721.6686.48.camel@marge.simson.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0803131230230.30831@jikos.suse.cz>


On Thu, 2008-03-13 at 12:31 +0100, Jiri Kosina wrote:
> On Thu, 13 Mar 2008, Mike Galbraith wrote:
> 
> > > I'm not sure if it's the same issue or not, they don't repeat 
> > > "forever" for me, it just makes my speeellllliingggg llllooookkk 
> > > teerrriibbblle. Like that. Before this happens, letters usually stop 
> > > appearing on screen as I'm typing. I usually stop typing at that 
> > > point, since I know it will just become a mess.
> > Yes, that's the symptom I was refering to.  If you see that under
> > reasonable CPU load, and _without_ major swapping going on, then I'd be
> > suspicious of scheduler trouble.  Swap can definitely keep X off the cpu
> > for extended periods, and that seems to be what triggers the repeated
> > keys behavior.  (I've never troubleshot it, so must say _seems_)
> 
> I have a hard time calling this a kernel scheduler trouble. My 
> understanding is that X are sometimes unhappy how kernel schedules them 
> when under load, and that triggers bug in X autorepeat code.

Only if X is not getting CPU for long periods without swapping would I
become suspicious of the scheduler.  We recently had exactly this
trouble with the fair groups load balancing code (now reverted) and CPU
bound loads.  The bug is a symptom of latency woes, and the scheduler is
just one potential source worth watching.  In the heavy swapping case,
it's unlikely to be scheduler trouble, and yes, the bug lies elsewhere.

	-Mike


  reply	other threads:[~2008-03-13 12:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 23:32 Keys get stuck Fred .
2008-03-12  0:04 ` Andrew Morton
2008-03-12  8:48 ` Sebastien Dugue
2008-03-12 10:32 ` Jiri Kosina
2008-03-12 10:44   ` David Newall
2008-03-12 14:47     ` Theodore Tso
2008-03-12 15:20       ` Stephen Hemminger
2008-03-12 16:47       ` David Newall
2008-03-12 16:49         ` Jiri Kosina
2008-03-12 21:22           ` Hans-Peter Jansen
2008-03-13  5:42             ` Mike Galbraith
2008-03-13  9:48               ` Jan Knutar
2008-03-13 11:28                 ` Mike Galbraith
2008-03-13 11:31                   ` Jiri Kosina
2008-03-13 12:02                     ` Mike Galbraith [this message]
2008-03-13 12:02                   ` Carlos R. Mafra
2008-03-13 12:06                     ` Jiri Kosina
2008-03-13 12:19                       ` Carlos R. Mafra
2008-03-13 12:21                     ` Mike Galbraith
2008-03-13 14:18                     ` Helge Hafting
2008-03-13 15:13                       ` Swap makes X unfair (was Re: Keys get stuck) Carlos R. Mafra
2008-03-14 11:02                         ` Helge Hafting
2008-03-15 22:11                           ` Carlos R. Mafra
2008-03-16 15:27                           ` Jan Knutar
2008-03-14 18:34                       ` Keys get stuck Pavel Machek
2008-03-13 17:14     ` Pavel Machek
2008-03-13 17:56       ` Fred .
2008-03-13 18:03         ` Pavel Machek
2008-03-14  9:21       ` Jiri Kosina
2008-03-14 18:24         ` Pavel Machek
2008-03-14 21:34           ` Lennart Sorensen
2008-03-14 13:30       ` Lennart Sorensen
2008-03-14 19:35         ` Pavel Machek
2008-03-13 13:01 ` Mark Lord
     [not found] <a6meN-2aj-39@gated-at.bofh.it>
     [not found] ` <a6wxo-1xY-1@gated-at.bofh.it>
     [not found]   ` <a6wQO-1YG-1@gated-at.bofh.it>
     [not found]     ` <a6Zgb-5Hj-55@gated-at.bofh.it>
     [not found]       ` <a7iiO-2fq-39@gated-at.bofh.it>
2008-03-14 20:20         ` Bodo Eggert

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=1205409721.6686.48.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=davidn@davidnewall.com \
    --cc=eldmannen@gmail.com \
    --cc=hpj@urpla.net \
    --cc=jk-lkml@sci.fi \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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