RE: kernel ipsec error

[Ben Hutchings <bhutchings@solarflare.com>]

On Tue, 2012-06-12 at 08:31 +0200, Marco Berizzi wrote:
> 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?

Given that you saw this after 12 days, I would think somewhere between
an hour and a day would be appropriate.

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.