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: Mon, 3 Apr 2006 20:40:48 -0700 [thread overview]
Message-ID: <20060403204048.092db2cc.akpm@osdl.org> (raw)
In-Reply-To: <4431001C.5080905@e-dict.net>
Ingo Freund <Ingo.Freund@e-dict.net> wrote:
>
> Hi,
>
> on our database machine with 4 GB RAM and 2 XEON CPUs I got the
> following kernel messages.
> There are 2 GB RAM declared as shared memory for database usage.
> Can anybody explain to me what happened and -may be- why?
>
You have a kernel memory leak.
>
> Apr 2 10:55:09 widbrz01 kernel: oom-killer: gfp_mask=0xd0, order=0
It was a GFP_KERNEL allocation.
> Apr 2 10:56:10 dbm kernel: Normal free:3168kB min:3756kB low:4692kB high:5632kB active:700kB inactive:548kB present:901120kB
There's a grand total of 1.2MB of ZONE_NORMAL memory on the LRU. The rest
(900MB-odd) is lost.
> 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.
next prev parent reply other threads:[~2006-04-04 3:41 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 [this message]
2006-04-04 8:31 ` Ingo Freund
2006-04-04 8:54 ` Andrew Morton
-- 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=20060403204048.092db2cc.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.