mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Larson <plars@austin.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: __alloc_pages: 0-order allocation failed
Date: 24 Sep 2001 08:13:42 +0000	[thread overview]
Message-ID: <1001319223.4613.34.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0109240810300.1593-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0109240810300.1593-100000@freak.distro.conectiva>

On 24 Sep 2001 08:12:20 -0300, Marcelo Tosatti wrote:
> 
> 
> On Mon, 24 Sep 2001, Jacek [iso-8859-2] Pop³awski wrote:
> 
> > I just installed 2.4.10, and...
> > 
> > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c0126c2e
> > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c0126c2e
> > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c0126c2e
> > VM: killing process donkey_s
...

I'm getting a lot of this with 2.4.10 also.  At the time, I had KDM
running, but I was coming into the box over telnet and running the
latest released version of LTP.  The test it appeared to be on at the
time was a filesystem test called growfiles.  Nothing else was running
other than these things and standard system services.  The machine has
256 MB of ram, and 512 MB swap.  The order that things got killed in
were sadc, sar, kdm, X, in.telnetd, xinetd (ouch).


__alloc_pages: 0-order allocation failed (gfp=0xf0/0) from c012b9b2
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c012b9b2
VM: killing process xinetd
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c012b9b2
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c012b9b2
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0) from c012b9b2

Thanks,
Paul Larson


  reply	other threads:[~2001-09-24 13:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24  2:02 Jacek Popławski
2001-09-24 11:12 ` Marcelo Tosatti
2001-09-24  8:13   ` Paul Larson [this message]
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  9:01   ` Paul Larson
2001-09-24 15:54   ` Olaf Hering
2001-09-24 16:06     ` Olaf Hering
2001-09-24 21:03   ` Jacek Popławski
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=1001319223.4613.34.camel@plars.austin.ibm.com \
    --to=plars@austin.ibm.com \
    --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

all inboxes | Powered by JetHome®