Re: I have a blaze of 353 page allocation failures, all alike

[Christoph Lameter <cl@linux.com>]

On Wed, 16 Feb 2011, Peter Kruse wrote:

> > How many buffers are configured at the various levels for the device that
> > is receiving messages? I guess that may be a bit on the high side?
>
> hm, I'm not sure if I know what you want mean or want me to do.

NICs typically can be configured via ethtool for various queue sizes. Also
ifconfig can do some queue config. The ip tool too etc. Maybe Eric can
have a look at this. Looks like its an sk_clone from an interrupt context
that is causing the trouble.

> > The call traces are sufficient but the traces vanished when I hit reply.
> > Include them inline next time. It would be good to have the log starting
> > at the last system boot. There is some information cut off that I would to
> > see.
>
> Ok, I attach the gzipped kern.log.

We still do not have the messages from bootup. I can only see the OOM
messages itself not how the kernel booted up.

> > A significant amount of memory has been allocated to reclaimable slabs.
> > I guess these are the socket buffers?
> >
> > Feb 10 11:59:49 beosrv1-t kernel: [1968911.211777] Node 0 Normal
> > free:965164kB min:917952kB low:1147440kB high:1376928kB
> > active_anon:2742680kB inactive_anon:293184kB active_file:4801512kB
> > inactive_file:11129708kB unevictable:0kB isolated(anon):0kB
> > isolated(file):0kB present:21719040kB mlocked:0kB dirty:600kB
> > writeback:0kB mapped:26356kB shmem:4896kB slab_reclaimable:1780208kB
> > <-----!!
> > slab_unreclaimable:199576kB kernel_stack:1576kB pagetables:22956kB
> > unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0
> > all_unreclaimable? no
> >
> > Could you try to reduce the number of network buffers?
>
> which parameter?

Ethtool, ifconfig and then there are various parameters in
/proc/sys/net/ipv4.