mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Andrey Nekrasov <andy@spylog.ru>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.8/2.4.9 problem
Date: Mon, 20 Aug 2001 23:20:37 +0200	[thread overview]
Message-ID: <20010820211403Z16263-32383+585@humbolt.nl.linux.org> (raw)
In-Reply-To: <200108171310.PAA26032@lambik.cc.kuleuven.ac.be> <20010819205452Z16128-32383+429@humbolt.nl.linux.org> <20010820011356.A6667@spylog.ru>
In-Reply-To: <20010820011356.A6667@spylog.ru>

On August 19, 2001 11:13 pm, Andrey Nekrasov wrote:
> Hello.
> 
> I am have problem with "kernel: __alloc_pages: 0-order allocation failed."
> 
> 1. syslog kern.*
> 
>    ...
> 	 Aug 19 12:28:16 sol kernel: __alloc_pages: 0-order allocation failed.
> 	 Aug 19 12:28:37 sol last message repeated 364 times
> 	 Aug 19 12:29:17 sol last message repeated 47 times
> [etc]

Could you please try it with this patch, which will tell us a little more 
about what's happening (patch -p0):

--- ../2.4.9.clean/mm/page_alloc.c	Thu Aug 16 12:43:02 2001
+++ ./mm/page_alloc.c	Mon Aug 20 22:05:40 2001
@@ -502,7 +502,7 @@
 	}
 
 	/* No luck.. */
-	printk(KERN_ERR "__alloc_pages: %lu-order allocation failed.\n", order);
+	printk(KERN_ERR "__alloc_pages: %lu-order allocation failed (gfp=0x%x/%i).\n", order, gfp_mask, !!(current->flags & PF_MEMALLOC));
 	return NULL;
 }
 

  reply	other threads:[~2001-08-20 21:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 13:10 2.4.8/2.4.9 VM problems Frank Dekervel
2001-08-19 21:00 ` Daniel Phillips
2001-08-19 21:13   ` 2.4.8/2.4.9 problem Andrey Nekrasov
2001-08-20 21:20     ` Daniel Phillips [this message]
2001-08-23 10:04       ` Andrey Nekrasov
2001-08-23 14:46         ` Daniel Phillips
2001-08-23 15:39         ` Stephan von Krawczynski
2001-08-23 18:05           ` Daniel Phillips
2001-08-20 15:40   ` 2.4.8/2.4.9 VM problems Mike Galbraith
2001-08-20 17:10     ` Daniel Phillips
2001-08-20 19:14       ` Mike Galbraith
2001-08-20 20:34         ` Daniel Phillips
2001-08-20 19:12           ` Marcelo Tosatti
2001-08-20 21:40             ` Daniel Phillips
2001-08-20 20:08               ` Marcelo Tosatti
2001-08-20 20:16                 ` Marcelo Tosatti
2001-08-20 22:54                   ` Daniel Phillips
2001-08-20 21:50                     ` Marcelo Tosatti
2001-08-20 23:29                       ` Daniel Phillips
2001-08-20 22:05                         ` Marcelo Tosatti
2001-08-20 23:54                           ` Daniel Phillips
2001-08-21  1:55                             ` Rik van Riel
2001-08-21  3:51                               ` Daniel Phillips
2001-08-21  3:58                                 ` Rik van Riel
2001-08-21  4:11                                   ` Daniel Phillips
2001-08-21  4:08                                     ` Rik van Riel
2001-08-20 21:44               ` Rik van Riel
2001-08-20 22:47                 ` Daniel Phillips
2001-08-21  4:52           ` Mike Galbraith
2001-08-21  5:14             ` Rik van Riel

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=20010820211403Z16263-32383+585@humbolt.nl.linux.org \
    --to=phillips@bonn-fries.net \
    --cc=andy@spylog.ru \
    --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®