public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.23-rc3-mm1 oom-killer gets invoked
Date: Thu, 23 Aug 2007 03:00:53 +0530	[thread overview]
Message-ID: <46CCAB0D.80507@linux.vnet.ibm.com> (raw)
In-Reply-To: <46CCA14A.6060103@linux.vnet.ibm.com>

Kamalesh Babulal wrote:
> Hi Andrew,
> 
> I see the oom-killer getting invoked many times on the
> 2.6.23-rc3-mm1 kernel and have attached the complete console
> log and config file.
> 
> ========================================================
> cc1 invoked oom-killer: gfp_mask=0x280d2, order=0, oomkilladj=0
> 
> [<c0147386>] out_of_memory+0x70/0xf6
> 
> [<c01484c4>] <4>cc1 invoked oom-killer: gfp_mask=0x201d2, order=0,
> oomkilladj=0
> 
> [<c0147386>] out_of_memory+0x70/0xf6
> 
> [<c01484c4>] __alloc_pages+0x21b/0x2a8
> 
> [<c0173168>] mntput_no_expire+0x11/0x6e
> 
> [<c0149f29>] __do_page_cache_readahead+0xc8/0x13a
> 
> [<c014535b>] filemap_nopage+0x164/0x30d
> 
> [<c0150c7d>] do_no_page+0x91/0x2fb
> 
> [<c0151201>] __handle_mm_fault+0x151/0x2bc
> 
> [<c016000f>] do_filp_open+0x25/0x39
> 
> [<c0115990>] do_page_fault+0x2a3/0x5f7
> 
> [<c01156ed>] do_page_fault+0x0/0x5f7
> 
> [<c03336c4>] error_code+0x7c/0x84
> 
> [<c0330000>] packet_rcv+0xfd/0x2d7
> 
> =======================
> 
> DMA per-cpu:
> 
> CPU    0: Hot: hi:    0, btch:   1 usd:   0   Cold: hi:    0, btch:   1
> usd:   0
> 
> CPU    1: Hot: hi:    0, btch:   1 usd:   0   Cold: hi:    0, btch:   1
> usd:   0
> 
> CPU    2: Hot: hi:    0, btch:   1 usd:   0   Cold: hi:    0, btch:   1
> usd:   0
> 
> CPU    3: Hot: hi:    0, btch:   1 usd:   0   Cold: hi:    0, btch:   1
> usd:   0
> 
> Normal per-cpu:
> 
> CPU    0: Hot: hi:  186, btch:  31 usd:  67   Cold: hi:   62, btch:  15
> usd:  57
> 
> CPU    1: Hot: hi:  186, btch:  31 usd: 170   Cold: hi:   62, btch:  15
> usd:  57
> 
> CPU    2: Hot: hi:  186, btch:  31 usd: 126   Cold: hi:   62, btch:  15
> usd:  50
> 
> CPU    3: Hot: hi:  186, btch:  31 usd:  50   Cold: hi:   62, btch:  15
> usd:  19
> 
> HighMem per-cpu:
> 
> CPU    0: Hot: hi:  186, btch:  31 usd:  21   Cold: hi:   62, btch:  15
> usd:  10
> 
> CPU    1: Hot: hi:  186, btch:  31 usd:  23   Cold: hi:   62, btch:  15
> usd:  19
> 
> CPU    2: Hot: hi:  186, btch:  31 usd:   7   Cold: hi:   62, btch:  15
> usd:  27
> 
> CPU    3: Hot: hi:  186, btch:  31 usd:  20   Cold: hi:   62, btch:  15
> usd:  56
> 
> Active:228916 inactive:238880 dirty:0 writeback:0 unstable:0
> 

Hmm... looks very interesting looks like you have ~1.8 GB (assuming page size
is equal to 4k). The log shows that OOM occurred several times.

Kamalesh, how much memory do you have the on the system and what test were
you running when you hit this problem? Is the problem reproducible? What is
the configured swap size?


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

      parent reply	other threads:[~2007-08-22 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 20:49 [BUG] 2.6.23-rc3-mm1 oom-killer gets invoked Kamalesh Babulal
2007-08-22 21:22 ` Andrew Morton
2007-08-22 21:30 ` Balbir Singh [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=46CCAB0D.80507@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamalesh@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox