All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-kernel-news@e-dict.net
Cc: Ingo.Freund@e-dict.net, linux-kernel@vger.kernel.org
Subject: Re: out of memory
Date: Tue, 4 Apr 2006 01:54:32 -0700	[thread overview]
Message-ID: <20060404015432.255fe0aa.akpm@osdl.org> (raw)
In-Reply-To: <44322EC5.5030006@e-dict.net>

Ingo Freund <Ingo.Freund@e-dict.net> wrote:
>

Please don't edit Cc:'s when working with kernel developers - just do
reply-to-all.

> Andrew Morton wrote:
> > Ingo Freund <Ingo.Freund@e-dict.net> wrote:
> >> Apr  2 10:56:11 dbm kernel: 8538 pages slab
> > 
> > and it's not in slab.
> > 
> >> Apr  2 10:56:11 dbm kernel: Symbols match kernel version 2.6.13.
> > 
> > Boy, 2.6.13 was a long time ago - I'm sure we fixed many leaks since then,
> > but I do not recall any particular patch which might fix this, sorry.
> > 
> > Your best option would be to seek a kernel upgrade.
> 
> I'll give a try to the last kernel version

OK, 2.6.16.1 would suit.

> Is there a way to get those kernel/memory information from time
> to time from the running system which I found in the syslog file?

/proc/meminfo gives a decent summary.

To watch your ZONE_NORMAL disappearing it would be better to monitor
/proc/zoneinfo.  There you'll see `free', `active', `inactive' and
`present'.  In /proc/meminfo you'll find the slab utilisation.

It should be approximately true that free+active+inactive+slab = present.

  reply	other threads:[~2006-04-04  8:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 10:59 out of memory Ingo Freund
2006-04-04  3:40 ` Andrew Morton
2006-04-04  8:31   ` Ingo Freund
2006-04-04  8:54     ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-23 15:57 Out " Luca Ferrari
2004-12-23 17:08 ` chuck gelm
     [not found] <31E38B53D182D51195FA00508BE3A33402CE4C9B@zwnbc004.cala.nortel.com>
2003-10-08 12:36 ` out " qhwang
2003-10-08 15:07 ` qhwang
2003-10-08 15:22   ` ronkhu
2003-10-08 16:31     ` qhwang
     [not found]       ` <1065630558.3f843b5e20715@www.correo.unam.mx>
2003-10-08 16:45         ` qhwang
2003-10-09 11:00     ` qhwang
2003-10-08 12:44 Sandro Dangui
2003-10-08 13:31 ` Mariano Moreyra
2003-10-08 13:38   ` Piyush Jain
2003-10-08 11:34 qhwang
2003-02-12 17:29 Balram Adlakha

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=20060404015432.255fe0aa.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Ingo.Freund@e-dict.net \
    --cc=linux-kernel-news@e-dict.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.