From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.6.29-rc3: page allocation failure
Date: Fri, 30 Jan 2009 09:59:18 +0100 [thread overview]
Message-ID: <1233305958.4495.157.camel@laptop> (raw)
In-Reply-To: <a4423d670901300022w1d2fe742kddc94869cce2097d@mail.gmail.com>
On Fri, 2009-01-30 at 11:22 +0300, Alexander Beregalov wrote:
> rtorrent: page allocation failure. order:1, mode:0x4020
> Pid: 2161, comm: rtorrent Not tainted 2.6.29-rc3 #1
> Call Trace:
Unless its a very frequent phenomenon, I'd not worry too much about
this.
GFP_ATOMIC allocations (like the one you had here) can fail at any time,
and !0 order even more so.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-01-30 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 8:22 Alexander Beregalov
2009-01-30 8:59 ` Peter Zijlstra [this message]
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=1233305958.4495.157.camel@laptop \
--to=peterz@infradead.org \
--cc=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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