From: Ben Hutchings <bhutchings@solarflare.com>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: kernel ipsec error
Date: Mon, 11 Jun 2012 18:49:23 +0100 [thread overview]
Message-ID: <1339436963.2665.5.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <DUB108-W3906ACEA67D9618490CB02B2F70@phx.gbl>
On Mon, 2012-06-11 at 14:45 +0200, Marco Berizzi wrote:
> Hello everybody.
>
> After 12 days uptime I got this message.
> Linux is 3.3.5 32bit, running openswan
> (this is an ipsec gateway/netfilter
> firewall) and squid.
>
> Jun 11 12:53:02 Pleiadi kernel: SLUB: Unable to allocate memory on node -1 (gfp=0x20)
> Jun 11 12:53:02 Pleiadi kernel: cache: kmalloc-2048, object size: 2048, buffer size: 2048, default order: 2, min order: 0
> Jun 11 12:53:02 Pleiadi kernel: node 0: slabs: 61, objs: 476, free: 0
> Jun 11 12:53:02 Pleiadi kernel: kworker/0:2: page allocation failure: order:0, mode:0x4020
So a single page allocation in atomic (non-sleeping) context failed.
[...]
> Jun 11 12:53:02 Pleiadi kernel: Free swap = 130908kB
> Jun 11 12:53:02 Pleiadi kernel: Total swap = 151164kB
> Jun 11 12:53:02 Pleiadi kernel: 40944 pages RAM
[...]
Not too surprising with this little RAM available (swap didn't help
since we couldn't wait for swap-out).
There could be a memory leak, but you would need to read /proc/meminfo
and /proc/slabinfo at intervals to work out whether that was the case.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-06-11 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 12:45 kernel ipsec error Marco Berizzi
2012-06-11 17:49 ` Ben Hutchings [this message]
2012-06-12 6:31 ` Marco Berizzi
2012-06-12 16:53 ` Ben Hutchings
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=1339436963.2665.5.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=pupilla@hotmail.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