From: Udo van den Heuvel <udovdh@xs4all.nl>
To: David Rientjes <rientjes@google.com>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: 3.6.11: khubd issue SLAB related?
Date: Wed, 13 Mar 2013 17:23:14 +0100 [thread overview]
Message-ID: <5140A7F2.5080203@xs4all.nl> (raw)
In-Reply-To: <alpine.DEB.2.02.1303111410470.4160@chino.kir.corp.google.com>
On 2013-03-11 22:23, David Rientjes wrote:
> On Fri, 8 Mar 2013, Udo van den Heuvel wrote:
>
>> [3663200.799579] SLAB: Unable to allocate memory on node 0 (gfp=0xd0)
>> [3663200.799581] cache: size-65536, object size: 65536, order: 4
>> [3663200.799583] node 0: slabs: 6/6, objs: 6/6, free: 0
>> [3663200.799585] pwc: Oops, could not allocate memory for pwc_device.
>
> You have memory freed, but like your earlier page allocation failure on
> mount, it is too fragmented. This is an order-4 page allocation, the
> kmalloc() of struct pwc_device, and you don't even have any order-3 pages
> that are available. Are you running with CONFIG_COMPACTION enabled?
Yes.
> If not, enable it and try again, or get root and manually try to
> defragment memory by doing echo 1 > /proc/sys/vm/compact_memory.
This needs to be done regularly, I assume?
> If so, try killing a memory hogging process to free some memory and
> attempt to get some higher order pages available.
It's a 8GB box (7.5GB available to software) with modest load. Mostly
email & web browsing, some torrents, nntp stuff, etc. Nothing weird.
Around 4.8G in buffers/cache right now.
Why is this issue occurring?
Why did I not see this in the past?
Udo
next prev parent reply other threads:[~2013-03-13 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 13:11 3.6.11: khubd issue SLAB related? Udo van den Heuvel
2013-03-08 13:15 ` Udo van den Heuvel
2013-03-11 21:23 ` David Rientjes
2013-03-13 16:23 ` Udo van den Heuvel [this message]
2013-03-13 23:36 ` 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=5140A7F2.5080203@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=hdegoede@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox