From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pre5 VM livelock
Date: Wed, 31 Oct 2001 00:18:47 +0100 [thread overview]
Message-ID: <20011031001847.F1340@athlon.random> (raw)
In-Reply-To: <3BDF1999.CAF5D101@mandrakesoft.com> <Pine.LNX.4.33.0110301436550.1188-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0110301436550.1188-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, Oct 30, 2001 at 02:49:27PM -0800
On Tue, Oct 30, 2001 at 02:49:27PM -0800, Linus Torvalds wrote:
>
> On Tue, 30 Oct 2001, Jeff Garzik wrote:
> >
> > Key symptoms: Free swab 0Kb according to sysrq-m, and several processes
> > in run state according to sysrq-t.
>
> What are the stack traces for the processes (ie "Ctrl-ScrollLock")
>
> It actually _sounds_ like you're out-of-memory for real, you have no swap
> left, and you have only four pages in the swap cache which implies that
> the system has tried very very hard to get rid of the pages you _did_
> write to swap.
>
> That, in turn, sounds like a memory leak. You've got 38578 pages on the
I agree it's oom, I think it's the infinite loop, it probably thinks
this memory is freeable but maybe it's all anonymous mlocked memory, or
maybe there's no swap at all that is equivalent for the vm.
I think it's not reproducible in -aa.
Andrea
next prev parent reply other threads:[~2001-10-30 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 21:20 pre5 VM livelock Jeff Garzik
2001-10-30 22:46 ` Andrea Arcangeli
2001-10-30 22:49 ` Linus Torvalds
2001-10-30 23:18 ` Andrea Arcangeli [this message]
2001-10-30 23:21 ` Linus Torvalds
2001-10-30 23:43 ` Jeff Garzik
2001-10-31 0:10 ` Linus Torvalds
2001-10-31 9:42 ` Marcelo Tosatti
2001-10-31 11:34 ` Jeff Garzik
2001-10-31 10:23 ` Marcelo Tosatti
2001-10-30 23:40 ` Linus Torvalds
2001-10-30 23:45 ` Jeff Garzik
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=20011031001847.F1340@athlon.random \
--to=andrea@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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