All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: <IRQ> [<ffffffff810c9204>] ? __alloc_pages_nodemask+0x622/0x696
Date: Sat, 05 Mar 2011 19:20:54 -0800	[thread overview]
Message-ID: <4D72FD96.6020702@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103051847100.8779@chino.kir.corp.google.com>

On 03/05/2011 06:50 PM, David Rientjes wrote:
> On Sat, 5 Mar 2011, Justin Mattock wrote:
>
>> [  339.787008] SLUB: Unable to allocate memory on node -1 (gfp=0x20)
>> [  339.787008]   cache: kmalloc-8192, object size: 8192, buffer size:
>> 8264, default order: 3, min order: 2
>> [  339.787008]   kmalloc-8192 debugging increased min order, use
>> slub_debug=O to disable.
>> [  339.787008]   node 0: slabs: 181, objs: 543, free: 0
>> [  339.790575] skbuff alloc of size 3904 failed
>> [  339.823775] swapper: page allocation failure. order:2, mode:0x4020
>> [  339.823781] Pid: 0, comm: swapper Not tainted 2.6.38-rc7-00143-gd1b152c #7
>> [  339.823783] Call Trace:
>> [  339.823786]<IRQ>   [<ffffffff810c9204>] ? __alloc_pages_nodemask+0x622/0x696
>> [  339.823811]  [<ffffffffa015a077>] ? ath_rxbuf_alloc+0x29/0x9a [ath]
>> [  339.823815]  [<ffffffff810f67cf>] ? new_slab+0x7b/0x1c6
>> [  339.823819]  [<ffffffffa015a077>] ? ath_rxbuf_alloc+0x29/0x9a [ath]
>> [  339.823823]  [<ffffffff810f6dd6>] ? T.925+0x163/0x29c
>> [  339.823827]  [<ffffffff810c4ecc>] ? mempool_destroy+0xf/0x17
>> [  339.823832]  [<ffffffffa015a077>] ? ath_rxbuf_alloc+0x29/0x9a [ath]
>> [  339.823836]  [<ffffffff810f895a>] ? __kmalloc_track_caller+0xfe/0x190
>>
>
> Order-2 atomic allocations are always going to be difficult since we can't
> do synchronous compaction or reclaim, but I'd try the suggestion shown
> above: boot with slub_debug=O or disable slub debugging so that
> kmalloc-8192 is actually order-1 like it should be.
>

alright! I will leave that setting on in the boot options to see if this 
happens again.

Justin P. Mattock

  reply	other threads:[~2011-03-06  3:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05  8:25 <IRQ> [<ffffffff810c9204>] ? __alloc_pages_nodemask+0x622/0x696 Justin Mattock
2011-03-06  2:50 ` David Rientjes
2011-03-06  3:20   ` Justin P. Mattock [this message]
2011-03-09  4:26   ` Justin P. Mattock
2011-03-09 20:57     ` David Rientjes
2011-03-09 21:18       ` Justin P. Mattock
2011-03-09 21:54         ` Christoph Lameter
2011-03-10  0:05           ` Bob Copeland
2011-03-15 20:59             ` Luis R. Rodriguez
2011-03-15 21:28               ` Justin P. Mattock
2011-03-15 22:13                 ` Luis R. Rodriguez
2011-03-15 23:56                   ` Justin P. Mattock

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=4D72FD96.6020702@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    /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.