From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-mm@kvack.org, Michael L Torrie <torriem@cs.byu.edu>,
Andrea Arcangeli <andrea@suse.de>
Subject: Re: [torriem@cs.byu.edu: VM: do_try_to_free_pages failed in 2.2.17]
Date: Mon, 18 Sep 2000 17:01:24 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0009181659130.2325-100000@freak.distro.conectiva> (raw)
In-Reply-To: <20000918113131.J10210@redhat.com>
On Mon, 18 Sep 2000, Stephen C. Tweedie wrote:
> Hi all,
>
> Yet another 2.2.17-eats-my-VM report. Does anyone have proven patches
> other than reverting completely to the old 2.2 VM? There's been lots
> of discussion and hypothesising but no silver bullets so far.
>
> --Stephen
Have you read Andrea VM-global patch against 2.2.18pre ?
I have received 3 or 4 reports of success with them.
--
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/
prev parent reply other threads:[~2000-09-18 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-18 10:31 Stephen C. Tweedie
2000-09-18 20:01 ` Marcelo Tosatti [this message]
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.0009181659130.2325-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
--cc=torriem@cs.byu.edu \
/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