linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: "Figo.zhang" <zhangtianfei@leadcoretech.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	Wu Fengguang <fengguang.wu@intel.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Minchan Kim <minchan.kim@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rientjes@google.com" <rientjes@google.com>,
	figo1802 <figo1802@gmail.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: oom_killer crash linux system
Date: Wed, 20 Oct 2010 12:24:34 +0900 (JST)	[thread overview]
Message-ID: <20101020122137.1824.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1287543520.2074.1.camel@myhost>

> 
> > 
> > can you please try 1) invoke oom 2) get page-types -r again. I'm curious
> > that oom makes page accounting lost again. I mean, please send us oom 
> > log and "page-types -r" result.
> > 
> > thanks
> 
> ok, i do the experiment and catch the log:

thanks.


> active_anon:398375 inactive_anon:82967 isolated_anon:0 
>  active_file:81 inactive_file:429 isolated_file:32
>  unevictable:13 dirty:2 writeback:14 unstable:0
>  free:11942 slab_reclaimable:2391 slab_unreclaimable:3303
>  mapped:5617 shmem:33909 pagetables:2280 bounce:0

active_anon + inactive_anon + isolated_anon = 481342 pages ~= 1.8GB
Um, this oom doesn't makes accounting lost.

> here is the page-types log:
>              flags	page-count       MB  symbolic-flags long-symbolic-flags
> 
> 0x0000000000005828	     83024      324 ___U_l_____Ma_b___________________ uptodate,lru,mmap,anonymous,swapbacked
> 0x0000000000005868	    358737     1401 ___U_lA____Ma_b___________________ uptodate,lru,active,mmap,anonymous,swapbacked
>              total	    515071     2011

page-types show similar result.


The big difference is, previous and current are showing some different processes.
only previous has VirtualBox, only current has vmware-usbarbit, etc..

Can you use same test environment?



--
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:[~2010-10-20  3:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101018021126.GB8654@localhost>
     [not found] ` <1287389631.1997.9.camel@myhost>
     [not found]   ` <20101018180919.3AF8.A69D9226@jp.fujitsu.com>
     [not found]     ` <1287454058.2078.12.camel@myhost>
2010-10-19  2:59       ` KAMEZAWA Hiroyuki
2010-10-19  5:23         ` Minchan Kim
2010-10-19  5:26           ` KAMEZAWA Hiroyuki
2010-10-19  5:34             ` Minchan Kim
2010-10-20  1:35             ` Wu Fengguang
2010-10-20  2:06               ` Figo.zhang
2010-10-20  2:32                 ` KOSAKI Motohiro
2010-10-20  2:58                   ` Figo.zhang
2010-10-20  3:24                     ` KOSAKI Motohiro [this message]
2010-10-20  3:43                       ` Figo.zhang
2010-10-20  5:05                         ` Adam Jiang

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=20101020122137.1824.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=fengguang.wu@intel.com \
    --cc=figo1802@gmail.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.com \
    --cc=rientjes@google.com \
    --cc=zhangtianfei@leadcoretech.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