From: Rik van Riel <riel@conectiva.com.br>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu,
torvalds@transmeta.com
Subject: Re: [patch] 2.3.99-pre6-3 VM fixed
Date: Thu, 27 Apr 2000 16:56:11 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0004271647461.3919-100000@duckman.conectiva> (raw)
In-Reply-To: <20000427172832.D3792@redhat.com>
On Thu, 27 Apr 2000, Stephen C. Tweedie wrote:
> On Wed, Apr 26, 2000 at 10:36:10AM -0300, Rik van Riel wrote:
> >
> > The patch runs great in a variety of workloads I've tested here,
> > but of course I'm not sure if it works as good as it should in
> > *your* workload, so testing is wanted/needed/appreciated...
>
> Well, on an 8GB box doing a "mtest -m1000 -r0 -w12" (ie. create
> 1GB heap and fork off 12 writer sub-processes touching the heap
> at random), I get a complete lockup just after the system goes
> into swap. At one point I was able to capture an EIP trace
> showing the kernel looping in stext_lock and try_to_swap_out.
After half a day of heavy abuse, I've gotten my machine into
a state where it's hanging in stext_lock and swap_out...
Both cpus are spinning in a very tight loop, suggesting a
deadlock. (/me points finger at other code, I didn't change
any locking stuff :))
This suggests a locking issue. Is there any place in the kernel
where we take a write lock on tasklist_lock and do a lock_kernel()
afterwards?
Alternatively, the mm->lock, kernel_lock and/or tasklist_lock could
be in play all three... Could the changes to ptrace.c be involved
here?
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
Wanna talk about the kernel? irc.openprojects.net / #kernelnewbies
http://www.conectiva.com/ http://www.surriel.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-04-27 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-26 13:36 Rik van Riel
2000-04-27 16:28 ` Stephen C. Tweedie
2000-04-27 19:56 ` Rik van Riel [this message]
2000-04-27 20:20 ` Kanoj Sarcar
2000-04-27 21:24 ` Linus Torvalds
2000-04-28 15:50 ` Linus Torvalds
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=Pine.LNX.4.21.0004271647461.3919-100000@duckman.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.com \
/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