From: "George Glover" <zed@baldwinmail.org>
To: <akpm@digeo.com>
Cc: <pavel@ucw.cz>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.65: *huge* interactivity problems
Date: Mon, 24 Mar 2003 19:56:56 -0500 (EST) [thread overview]
Message-ID: <4818.68.40.176.184.1048553816.squirrel@mail.baldwinmail.org> (raw)
In-Reply-To: <20030324171936.680f98e2.akpm@digeo.com>
I also have a similar problem, when running setiathome with priority 1.
All _running_ applications remain interactive, anything requring disk
access, in particular starting a new program, causes things to block.
I've so far only been in X when this happens, mouse still moves, remote
applications update their windows fine, no lost keystrokes, it's when I
run something locally requiring disk IO.
Renicing setiathome to -19 causes the problem to vanish.
Dragging an xterm around seems to help it recover from a hang too.
> - How much memory does the machine have?
256
> - UP/SMP/preempt?
preempt
>
> - What do vmstat and top say?
3 1 2216 21008 27464 69920 0 0 0 0 1024 241 100 0 0 0
3 1 2216 20176 27464 69920 0 0 0 0 1024 249 100 0 0 0
3 1 2216 20176 27464 69920 0 0 0 0 1024 252 99 1 0 0
3 1 2216 21060 27464 69920 0 0 0 0 1025 236 100 0 0 0
> - Did it happen in 2.5.64? 2.5.63? 2.4.20?
2.5.64
> - Does it get better if you renice stuff?
Yes
> - What steps should others take to reproduce it?
Running setiathome with priority one seems to do it for me.
George
next prev parent reply other threads:[~2003-03-25 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 23:13 Pavel Machek
2003-03-25 1:19 ` Andrew Morton
2003-03-24 23:34 ` Pavel Machek
2003-03-24 23:45 ` CaT
2003-03-25 0:00 ` Pavel Machek
2003-03-25 0:04 ` CaT
[not found] ` <20030324181250.6a6be3f8.akpm@digeo.com>
[not found] ` <20030325064417.GA454@zip.com.au>
[not found] ` <20030324232444.0a9260fc.akpm@digeo.com>
2003-03-25 15:43 ` CaT
2003-03-25 0:56 ` George Glover [this message]
2003-03-26 4:05 George Glover
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=4818.68.40.176.184.1048553816.squirrel@mail.baldwinmail.org \
--to=zed@baldwinmail.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®