From: Philipp Herz - Profihost AG <p.herz@profihost.ag>
To: linux-kernel@vger.kernel.org
Subject: Vanilla-Kernel 3 - page allocation failure
Date: Tue, 18 Oct 2011 12:25:03 +0200 [thread overview]
Message-ID: <4E9D53FF.7090609@profihost.ag> (raw)
After updating kernel (x86_64) to stable version 3 there are a few
messages appearing in the kernel log such as
kworker/0:1: page allocation failure: order:1, mode:0x20
mysql: page allocation failure: order:1, mode:0x20
php5: page allocation failure: order:1, mode:0x20
Searching the net showed that these messages are known to occur since 2004.
Some people were able to get rid of them by setting
/proc/sys/vm/min_free_kbytes to a high enough value. This does not help
in our case.
Is there a kernel comand line argument to avoid these messages?
As of mm/page_alloc.c these messages are marked to be only warning
messages and would not appear if 'gpf_mask' was set to __GFP_NOWARN in
function warn_alloc_failed.
How does this mask get set? Is it set by the "external" process knocking
at the memory manager?
What is the magic behind the 'order' and 'mode'?
I'm not a subscriber, so please CC me a copy of messages related to the
subject. I'm not sure if I can help much by looking at the inside of the
kernel, but I will try my best to answer any questions concerning this
issue.
Best regards, Philipp
next reply other threads:[~2011-10-18 10:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 10:25 Philipp Herz - Profihost AG [this message]
2011-10-18 11:32 ` Vanilla-Kernel 3 - page allocation failure Thadeu Lima de Souza Cascardo
2011-10-18 12:07 ` Philipp Herz - Profihost AG
2011-10-18 12:38 ` Thadeu Lima de Souza Cascardo
2011-10-18 13:24 ` Philipp Herz - Profihost AG
2011-10-18 14:35 ` Thadeu Lima de Souza Cascardo
2011-10-19 6:45 ` Philipp Herz - Profihost AG
2011-10-18 15:51 ` Andi Kleen
2011-10-18 17:02 ` Dave Jones
2011-10-18 18:59 ` Andi Kleen
2011-10-19 1:58 ` David Rientjes
2011-10-24 6:33 ` Philipp Herz - Profihost AG
2011-10-24 7:03 ` Eric Dumazet
2011-10-24 7:21 ` Philipp Herz - Profihost AG
2011-10-24 8:01 ` Eric Dumazet
2011-10-24 8:19 ` Philipp Herz - Profihost AG
2011-10-24 8:29 ` Eric Dumazet
2011-10-24 8:36 ` Stefan Priebe - Profihost AG
2011-10-26 20:26 ` David Rientjes
2011-10-27 7:13 ` Philipp Herz - Profihost AG
2011-10-27 20:08 ` David Rientjes
2011-10-20 21:11 ` Valdis.Kletnieks
2011-10-21 6:36 ` Philipp Herz - Profihost AG
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 10:24 Philipp Herz - Profihost AG
2011-10-19 2:09 ` David Rientjes
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=4E9D53FF.7090609@profihost.ag \
--to=p.herz@profihost.ag \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.