From: Daniel Phillips <phillips@bonn-fries.net>
To: Gergely Madarasz <gorgo@thunderchild.debian.net>,
linux-kernel@vger.kernel.org
Subject: Re: vm problems
Date: Thu, 30 Aug 2001 00:02:27 +0200 [thread overview]
Message-ID: <20010829215542Z16262-32383+2341@humbolt.nl.linux.org> (raw)
In-Reply-To: <20010829131419.Z6202@thunderchild.ikk.sztaki.hu> <20010829134757.A6202@thunderchild.ikk.sztaki.hu>
In-Reply-To: <20010829134757.A6202@thunderchild.ikk.sztaki.hu>
On August 29, 2001 01:47 pm, Gergely Madarasz wrote:
> On Wed, Aug 29, 2001 at 01:14:19PM +0200, Gergely Madarasz wrote:
> > Hello,
> >
> > I get hundreds of this error message:
> >
> > __alloc_pages: 0-order allocation failed.
> >
> > The machine is an IBM x250 with 4G ram, the kernel is vanilla 2.4.9 and
> > 2.4.9-ac3, no swap, running bonnie++. When the memory fills up with cache,
> > I start receiving the error message.
>
> actually I thought I was running 2.4.9-ac3, but no, and I see the message
> is commented out in 2.4.9-ac3. Does this mean that it doesn't mean
> anything serious? Some of my processes were stuck in uninterruptible
> sleep, I couldn't even shutdown correctly, so there are some problems.
Please try it again with this patch so we can see what kind of allocation is failing:
--- 2.4.9.clean/mm/page_alloc.c Thu Aug 16 12:43:02 2001
+++ 2.4.9/mm/page_alloc.c Mon Aug 20 22:05:40 2001
@@ -502,7 +502,8 @@
}
/* 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;
}
next prev parent reply other threads:[~2001-08-29 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 11:14 vm problems Gergely Madarasz
2001-08-29 11:47 ` Gergely Madarasz
2001-08-29 22:02 ` Daniel Phillips [this message]
2001-08-29 12:26 ` Stephan von Krawczynski
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=20010829215542Z16262-32383+2341@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=gorgo@thunderchild.debian.net \
--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;
as well as URLs for NNTP newsgroup(s).