public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Morten W. Petersen" <morten@nidelven-it.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fixing page allocation failure
Date: Thu, 18 Nov 2004 23:10:44 +1100	[thread overview]
Message-ID: <419C9144.2080605@yahoo.com.au> (raw)
In-Reply-To: <419C8756.3080709@nidelven-it.no>

Morten W. Petersen wrote:
> Hi all,
> 
> I have a server that a couple of times each day squirts out messages 
> about page allocation failures (python: page allocation failure. 
> order:3, mode:0x20).  What's the reason for this, and could it affect 
> the stability of the box?
> 
> The server that squirts these messages just crashed, for no apparent 
> reason, so that's why I'm wondering.  It's a UML box.  Also, I'm 
> wondering, are there any howto's for tweaking /proc settings so that the 
> machine becomes more stable?  Are there any settings for increasing the 
> verbosity of the kernel log so that the reason for a server crashing is 
> easier to find?
> 
> Thanks in advance, and please CC me any replies :)
> 
> Regards,
> 
> Morten

Yeah you can increase /proc/sys/vm/min_free_kbytes to help the problem.

There is a possibly better solution in the -mm kernels which should get
merged into 2.6 sooner or later - but there is still no way to guarantee
safety from allocation failures. If they cause crashes then that is a
bug, so report them here with traces and a description of the workload
and system hardware, etc.

Thanks
Nick

  reply	other threads:[~2004-11-18 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 11:28 Fixing page allocation failure Morten W. Petersen
2004-11-18 12:10 ` Nick Piggin [this message]
2004-11-19  2:01 ` Andrew Morton
2004-11-20  1:10   ` Morten W. Petersen
2004-11-20  3:57     ` Andrew Morton

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=419C9144.2080605@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morten@nidelven-it.no \
    /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