From: Nick Piggin <piggin@cyberone.com.au>
To: martin f krafft <madduck@madduck.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: scheduling problems in X with 2.6.0
Date: Thu, 08 Jan 2004 02:30:41 +1100 [thread overview]
Message-ID: <3FFC2621.7060808@cyberone.com.au> (raw)
In-Reply-To: <20040107102352.GA2954@piper.madduck.net>
martin f krafft wrote:
>Hi all,
>
>Ever since I moved to 2.6.0, I have been experiencing something I'd
>like to call scheduling problems while working in X. I have tried
>using preemptive mode, and turning it off, but the symptoms are the
>same:
>
>whenever there is continuous disk access (e.g. tar, rsync, dd),
>X will not respond for a couple of seconds every couple of seconds.
>With that I mean that the mouse will freeze as well as all screen
>output, and then resume after a couple of seconds.
>
>I wonder if I am the only one with that problem. The machine in
>question is a dual AMD 2400+ with 2Gb of RAM and a Maxtor DiamondMax
>drive spinning at 7200 RPM. The drive is configured as follows
>(hdparm):
>
Can you post 20 or so lines of 'vmstat 1' captured while the problem is
happening? See if you can see which lines correspond to X freezing (ie.
watch the xterm), but that might be impossible if everything freezes.
next prev parent reply other threads:[~2004-01-07 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 10:23 scheduling problems in X with 2.6.0 martin f krafft
2004-01-07 15:30 ` Nick Piggin [this message]
2004-01-07 17:46 ` martin f krafft
2004-01-08 15:34 ` Nick Piggin
2004-01-08 15:41 ` martin f krafft
2004-01-08 15:47 ` Nick Piggin
2004-01-08 15:42 ` martin f krafft
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=3FFC2621.7060808@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=madduck@madduck.net \
/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.