From: Dave Jones <davej@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: p.herz@profihost.ag, linux-kernel@vger.kernel.org
Subject: Re: Vanilla-Kernel 3 - page allocation failure
Date: Tue, 18 Oct 2011 13:02:04 -0400 [thread overview]
Message-ID: <20111018170204.GA10551@redhat.com> (raw)
In-Reply-To: <m2ipnmz49x.fsf@firstfloor.org>
On Tue, Oct 18, 2011 at 08:51:54AM -0700, Andi Kleen wrote:
> Philipp Herz - Profihost AG <p.herz@profihost.ag> writes:
>
> > 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
>
> You just ran out of memory.
>
> The problem here seems to be that the kernel is unable to communicate
> in a language you can understand.
>
> How do you think the message should have been phrased to make the
> issue more clear?
We get reports like this fairly regularly, usually accompanied by
"But I had lots of free memory and/or swap!"
The order/mode stuff is completely opaque to end-users, who have no
clue that there are different types of memory, and exhausting one type
can happen even when plenty of other memory is free.
I've been toying with the idea of hacking up a patch to turn those mode
flags into printing things like "mode:GFP_ATOMIC|GFP_NOIO" instead though, as I can
never remember those flags off the top of my head.
Still won't help end-users, but it would at least speed up diagnosing reports.
Dave
next prev parent reply other threads:[~2011-10-18 17:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 10:25 Vanilla-Kernel 3 - page allocation failure Philipp Herz - Profihost AG
2011-10-18 11:32 ` 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 [this message]
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
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=20111018170204.GA10551@redhat.com \
--to=davej@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.herz@profihost.ag \
/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).