public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: "Christian Bornträger" <linux-kernel@borntraeger.net>
Cc: "Marcelo Tosatti" <marcelo@conectiva.com.br>,
	"Paul Larson" <plars@austin.ibm.com>,
	"Linus Torvalds" <torvalds@transmeta.com>,
	"Jacek[iso-8859-2]Pop³awski" <jpopl@interia.pl>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: __alloc_pages: 0-order allocation failed
Date: Wed, 26 Sep 2001 01:01:49 +0200	[thread overview]
Message-ID: <20010926010149.U8350@athlon.random> (raw)
In-Reply-To: <1001319223.4613.34.camel@plars.austin.ibm.com> <Pine.LNX.4.21.0109240933390.1593-100000@freak.distro.conectiva> <20010926000922.I8350@athlon.random> <E15m0Wz-0002He-00@mrvdom01.schlund.de>
In-Reply-To: <E15m0Wz-0002He-00@mrvdom01.schlund.de>; from linux-kernel@borntraeger.net on Wed, Sep 26, 2001 at 12:16:53AM +0200

On Wed, Sep 26, 2001 at 12:16:53AM +0200, Christian Bornträger wrote:
> > too much permissive (vm-tweaks-1 does something similar but not that
> > permissive)
> 
> But it doesnt help neither.  I installed vm-tweaks-1 on a vanilla 2.4.10 and 
> still got an __alloc_pages: 0-order allocation failure
> I have no swap and 512 MB of RAM.

Could you enable CONFIG_DEBUG_GFP (kernel debugging menu) in 2.4.10aa1
and send me full traces of the faliures so I can better see where the
problem cames from? Thanks!

Andrea

  reply	other threads:[~2001-09-25 23:01 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 [this message]
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
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=20010926010149.U8350@athlon.random \
    --to=andrea@suse.de \
    --cc=jpopl@interia.pl \
    --cc=linux-kernel@borntraeger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=plars@austin.ibm.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