linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: sharyathi@in.ibm.com, linux-mm <linux-mm@kvack.org>
Subject: Re: [Bug 5494] New: OOM killer kills process on kernel boot up and system performance is very low
Date: Tue, 25 Oct 2005 11:27:13 -0700	[thread overview]
Message-ID: <1130264833.6831.77.camel@localhost.localdomain> (raw)
In-Reply-To: <20051025104516.4bd3798c.akpm@osdl.org>

On Tue, 2005-10-25 at 10:45 -0700, Andrew Morton wrote:
> bugme-daemon@kernel-bugs.osdl.org wrote:
> >
> >  http://bugzilla.kernel.org/show_bug.cgi?id=5494
> > 
> >             Summary: OOM killer kills process on kernel boot up and system
> >                      performance is very low
> >      Kernel Version: 2.6.14-rc4
> 
> You have an enormous memory leak.
> 
> 
> Active:1452 inactive:929 dirty:3 writeback:717 unstable:0 free:7065 slab:2779 mapped:1356 pagetables:464
> DMA free:6160kB min:68kB low:84kB high:100kB active:0kB inactive:2348kB present:16384kB pages_scanned:1o
> lowmem_reserve[]: 0 880 1519
> Normal free:21604kB min:3756kB low:4692kB high:5632kB active:276kB inactive:188kB present:901120kB pages
> lowmem_reserve[]: 0 0 5119
> HighMem free:496kB min:512kB low:640kB high:768kB active:5532kB inactive:1052kB present:655296kB pages_s
> lowmem_reserve[]: 0 0 0
> DMA: 2*4kB 3*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 0*2048kB 1*4096kB = 6160kB
> Normal: 1*4kB 20*8kB 36*16kB 10*32kB 3*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 4*4096kB = 21604kB
> HighMem: 0*4kB 0*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 496kB
> Swap cache: add 51244, delete 50404, find 25442/32337, race 0+13
> 
> And it's leaking highmem too, so it has to be user memory: pagecache or
> anoymous RAM.
> 
> I'm not too sure what to do really - something odd is happening because if
> this was happening generally then everyone in the world would be reporting
> it.
> 
> I'd suggest you try switching compiler versions, try disabling unneeded
> features in .config, see if you can identify any one which causes the leak.
> Ideally, use `git bisect' to identify when the problem started occurring. 
> 
> All very strange.
> 
> btw, what is this:
> 
> Starting readahead:  [  OK  ]

"readahead" is a init script in RedHat distro which does

    /usr/sbin/readahead `cat /etc/readahead.files` &

I guess it reads the files into pagecache.

(readahead(2)  -  Read  in advance one or more pages of a file
       within a page cache)


Thanks,
Badari

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-10-25 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200510251218.j9PCIOoo027509@fire-1.osdl.org>
2005-10-25 17:45 ` Andrew Morton
2005-10-25 18:27   ` Badari Pulavarty [this message]
2005-10-26 12:27     ` Nagesh Sharyathi

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=1130264833.6831.77.camel@localhost.localdomain \
    --to=pbadari@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=sharyathi@in.ibm.com \
    /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