mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Date: Mon, 19 Jan 2004 19:38:37 -0800	[thread overview]
Message-ID: <20040119193837.6369d498.akpm@osdl.org> (raw)
In-Reply-To: <7641.1074512162@gmcs3.local>

Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
>
> There seems to be a problem with 2.6.1 on my machine. It will be fine
>  for a matter of a few days and then this error will appear on the
>  console. The message then appears repeatedly and continuously. The
>  first I know is that my remote login shell ceases to respond. About the
>  only thing I can do is switch between virtual consoles (until I hit the
>  reset button).
> 
>  /var/log/messages shows:
>  kernel: cat: page allocation failure. order:0, mode:0x20
> 
>  Then the same for lots of other processes (pdflush, syslogd, klogd,
>  kswapd0, nfsd to name a few). I expect that after a point it is unable
>  to even log stuff so syslog is quiet after a while.
> 
>  It has happened three times now and on all occasions, I was untarring a
>  huge file on an XFS partition. I assume the problem is something to do
>  with VM. The machine has 1GB of RAM which should be plenty. For the
>  most part it is just serving NFS and NIS (to no more than about 10
>  clients).

Does the machine actually recover, or does it grind to a halt and need
resetting?

Is there much network receive happening at the time?

Are you using gig-E with large MTU's?

> If anyone can suggest any /proc variables I might change to reduce the
> risk of it doing this again, I would appreciate it. I tried increasing
> /proc/sys/vm/min_free_kbytes after the first time this happened. Not
> that I understand what that does: I searched the archives and it was
> mentioned in a vaguely relevant looking post.

Yup, min_free_kbytes is the right thing to increase.  Try it again, perhaps
increasing it by more - to 10000 or something like that.

min_free_kbytes will increase the amount of memory which the VM keeps in
reserve to satisfy interrupt-time memory allocation attempts - most
especially network receive.


You probably should apply this patch to tell us where the allocation
failures are coming from.  Make sure that CONFIG_KALLSYMS is enabled in
kernel config.


diff -puN mm/page_alloc.c~a mm/page_alloc.c
--- 25/mm/page_alloc.c~a	Mon Jan 19 19:34:09 2004
+++ 25-akpm/mm/page_alloc.c	Mon Jan 19 19:34:21 2004
@@ -674,6 +674,7 @@ nopage:
 		printk("%s: page allocation failure."
 			" order:%d, mode:0x%x\n",
 			p->comm, order, gfp_mask);
+		dump_stack();
 	}
 	return NULL;
 got_pg:

_


  parent reply	other threads:[~2004-01-20  3:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 11:36 Oliver Kiddle
2004-01-19 14:54 ` Mike Fedyk
2004-01-19 17:29   ` Oliver Kiddle
2004-01-19 18:12     ` Mike Fedyk
2004-01-20  3:38 ` Andrew Morton [this message]
2004-01-20  6:00   ` Nathan Scott
2004-01-20 17:08   ` Oliver Kiddle
2004-01-20 18:35     ` Mike Fedyk
2004-01-22  9:29       ` Oliver Kiddle
2004-01-22  9:59         ` Andrew Morton
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton
2004-08-24 22:57   ` David S. Miller

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=20040119193837.6369d498.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okiddle@yahoo.co.uk \
    /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®