All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Dave Airlie <airlied@gmail.com>, Dave Airlie <airlied@redhat.com>,
	David Howells <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Why is kslowd accumulating so much CPU time?
Date: Mon, 14 Jun 2010 17:46:46 -0400	[thread overview]
Message-ID: <20100614214646.GF6666@thunk.org> (raw)
In-Reply-To: <20100614184244.GA11480@elliptictech.com>

On Mon, Jun 14, 2010 at 02:42:44PM -0400, Nick Bowler wrote:
> 
> This sounds exactly like the issue I've been seeing on a T500 laptop, as
> well (GM45 board).  The slowdowns render the system essentially
> unusable, as it can spend a loooong time just moving the mouse cursor a
> few pixels on the screen.  During this time, nothing else on the display
> is updating (glxgears drops to 0fps).  Things generally seem to be
> working fine if I am not moving the mouse, or if I'm not running X.

I saw exactly the same behaviour when using the Ubuntu Karmic
userspace.  Basically, using a 2.6.35-rc2 (+ vt memory corrupter fix)
kernel, the system was essentially unusable.  Interestingly, the
problem went away (with the same kernel) once I updated to Ubuntu
Lucid.  I was going to mention that so that hopefully someone with far
more X.org-fu than I could figure out how much of this is a X server
bug, and how much of this was a kernel bug, but things worked just
*fine* with 2.6.34 kernel.

Occasionally it will happen that the mouse stops tracking, and then I
grumble and curse, and a few seconds later it resolves itself.  I
haven't had time to track it down; but the problem was breathtakingly
easy to reproduce with an Ubuntu Karmic userspace.  :-)

     		       	  	 		    - Ted

  reply	other threads:[~2010-06-14 21:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 18:36 Why is kslowd accumulating so much CPU time? Theodore Ts'o
2010-06-09 18:56 ` David Howells
2010-06-09 19:00   ` David Howells
2010-06-13  8:23 ` Dave Airlie
2010-06-13 19:49   ` tytso
2010-06-13 20:00     ` Dave Airlie
2010-06-14 18:42       ` Nick Bowler
2010-06-14 21:46         ` tytso [this message]
2010-06-15 17:25           ` Andy Whitcroft
2010-06-15 18:07             ` David Howells
2010-06-16 11:37               ` Andy Whitcroft
2010-06-16 13:33                 ` Andy Whitcroft
2010-06-16 14:36                 ` Nick Bowler
2010-06-16 14:55                   ` Andy Whitcroft
2010-06-17 13:25                     ` Nick Bowler

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=20100614214646.GF6666@thunk.org \
    --to=tytso@mit.edu \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.