From: Marco Berizzi <pupilla@hotmail.com>
To: <bhutchings@solarflare.com>
Cc: <netdev@vger.kernel.org>
Subject: RE: kernel ipsec error
Date: Tue, 12 Jun 2012 08:31:18 +0200 [thread overview]
Message-ID: <DUB108-W54AAF31BD3E442DF275349B2F60@phx.gbl> (raw)
In-Reply-To: <1339436963.2665.5.camel@bwh-desktop.uk.solarflarecom.com>
bhutchings@solarflare.com wrote:
> 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).
yes, this is really a very old hardware.
> 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.
Kindly, may you tell me which should be the intervals? One second? one minute?
next prev parent reply other threads:[~2012-06-12 6:31 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
2012-06-12 6:31 ` Marco Berizzi [this message]
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=DUB108-W54AAF31BD3E442DF275349B2F60@phx.gbl \
--to=pupilla@hotmail.com \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.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