From: "Jacek Popławski" <jpopl@interia.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: __alloc_pages: 0-order allocation failed
Date: Mon, 24 Sep 2001 23:03:46 +0200 [thread overview]
Message-ID: <20010924230345.A1540@localhost.localdomain> (raw)
In-Reply-To: <20010924040208.A624@localhost.localdomain> <Pine.LNX.4.21.0109240810300.1593-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0109240810300.1593-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Mon, Sep 24, 2001 at 08:12:20AM -0300
On Mon, Sep 24, 2001 at 08:12:20AM -0300, Marcelo Tosatti wrote:
> Jacek,
>
> You had available swap when the VM started to kill processes ?
Application eats whole memory, then started using swap, when swap used is 10MB
kernel starting to cry:
[root@localhost /root]# free
total used free shared buffers cached
Mem: 320616 317348 3268 0 120 304096
-/+ buffers/cache: 13132 307484
Swap: 104380 10208 94172
[root@localhost /root]# free
total used free shared buffers cached
Mem: 320616 318932 1684 0 136 305372
-/+ buffers/cache: 13424 307192
Swap: 104380 10072 94308
[root@localhost /root]# __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c0126c2e
free
total used free shared buffers cached
Mem: 320616 318884 1732 0 128 305636
-/+ buffers/cache: 13120 307496
Swap: 104380 10204 94176
[root@localhost /root]# __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c0126c2e
VM: killing process donkey_s
free
total used free shared buffers cached
Mem: 320616 318732 1884 0 116 305480
-/+ buffers/cache: 13136 307480
Swap: 104380 9312 95068
next prev parent reply other threads:[~2001-09-24 21:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 2:02 __alloc_pages: 0-order allocation failed Jacek Popławski
2001-09-24 11:12 ` Marcelo Tosatti
2001-09-24 8:13 ` Paul Larson
2001-09-24 9:01 ` Paul Larson
2001-09-24 12:38 ` Marcelo Tosatti
2001-09-24 11:35 ` Paul Larson
2001-09-24 15:12 ` Marcelo Tosatti
2001-09-24 19:48 ` tpepper
2001-09-26 13:48 ` Andrea Arcangeli
2001-09-24 15:33 ` Christian Bornträger
2001-09-25 22:09 ` Andrea Arcangeli
2001-09-25 21:25 ` Marcelo Tosatti
2001-09-25 23:05 ` Andrea Arcangeli
2001-09-26 18:15 ` tpepper
2001-09-26 18:29 ` Andrea Arcangeli
2001-09-25 22:16 ` Christian Bornträger
2001-09-25 23:01 ` Andrea Arcangeli
2001-09-25 23:10 ` Christian Bornträger
2001-09-25 23:19 ` Andrea Arcangeli
2001-09-25 23:24 ` Christian Bornträger
2001-09-25 23:46 ` Andrea Arcangeli
2001-09-26 7:29 ` Christian Bornträger
2001-09-24 15:54 ` Olaf Hering
2001-09-24 16:06 ` Olaf Hering
2001-09-24 21:03 ` Jacek Popławski [this message]
2001-09-24 21:11 ` Jacek Popławski
2001-09-24 12:58 ` Christian Bornträger
2001-09-24 13:05 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 12:09 Oliver König
2006-06-01 12:19 ` Jes Sorensen
2001-09-04 13:11 Martin MOKREJŠ
2001-09-04 16:12 ` Daniel Phillips
2001-09-07 12:53 ` Martin MOKREJŠ
2001-09-07 13:06 ` Martin MOKREJŠ
2001-09-07 20:43 ` Daniel Phillips
2001-09-07 21:00 ` Daniel Phillips
2001-09-12 13:06 ` Martin MOKREJŠ
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=20010924230345.A1540@localhost.localdomain \
--to=jpopl@interia.pl \
--cc=linux-kernel@vger.kernel.org \
/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