public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Leonid Petrov <nouser@lpetrov.net>
Cc: linux-kernel@vger.kernel.org, user@lpetrov.net
Subject: Re: Out of Memory: Killed process while 1 Gb is free
Date: Fri, 8 Oct 2004 08:06:37 -0300	[thread overview]
Message-ID: <20041008110636.GF16028@logos.cnet> (raw)
In-Reply-To: <E1CD2GS-0006EF-7b@server14.totalchoicehosting.com>

On Thu, Sep 30, 2004 at 10:50:36AM -0400, Leonid Petrov wrote:
> Summary: 
>     "Out of Memory: Killed process" when more than 1 Gb of free memory
>      is available.
> 
> Description:
>   My Linux-server after 2-10 days starts killing processes claiming
>   that it is "Out of memory". Top does not show any processess which
>   occupy more than several percent of memory. It always occur when 
>   the amount of available memory (1Gb) is about half of the total 
>   memory (2Gb). Killing a process does not help and the kernel 
>   continue mass murder till the state then it becomes non-operational. 
>   During agony vmstat showed that the occupied 1Gb of memory was used 
>   mainly by cache and buffers. Analazing kernel log I found 245 events 
>   for last 3 weeks. All events occured when anount of Normal memory 
>   was in the range [0,2052]Kb (and about 1Gb of free high memory). 
>   It did not occur before upgrade to 2.6.8.1. Out of memory events 
>   occured in both Hyperthreading enabled and Hyperthreading disabled 
>   mode.
> 
> Keywords:
>   Virtual memory managment

Hi,

There have been several changes in this area since 2.6.8.1, it 
would be nice if you can repeat the tests with a recent -mm kernel 
(where most of the changes are).

One information is that there are not many freeable pages in 
the normal zone (active+inactive) lists:

 DMA free:1904kB min:16kB low:32kB
high:48kB active:112kB inactive:0kB present:16384kB
Sep 30 08:53:22 lacerta kernel: protections[]: 8 476 732
Sep 30 08:53:22 lacerta kernel: Normal free:1512kB min:936kB low:1872kB
high:2808kB active:216kB inactive:436kB present:901120kB

For me it looks like you might be seeing a kernel memory leak (what else
could cause such condition?)

IIRC quite some kernel memory leaks have been fixed since 2.6.8.1 
(cdrom driver, NFS, ...)


      reply	other threads:[~2004-10-08 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 14:50 Out of Memory: Killed process while 1 Gb is free Leonid Petrov
2004-10-08 11:06 ` Marcelo Tosatti [this message]

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=20041008110636.GF16028@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouser@lpetrov.net \
    --cc=user@lpetrov.net \
    /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