From: Wu Fengguang <fengguang.wu@intel.com>
To: "Figo.zhang" <zhangtianfei@leadcoretech.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
figo1802 <figo1802@gmail.com>
Subject: Re: oom_killer crash linux system
Date: Wed, 20 Oct 2010 09:47:46 +0800 [thread overview]
Message-ID: <20101020014746.GA8338@localhost> (raw)
In-Reply-To: <1287538607.2031.5.camel@myhost>
On Wed, Oct 20, 2010 at 09:36:47AM +0800, Figo.zhang wrote:
> >
> > >
> > > echo 5 > /proc/sys/vm/dirty_ratio
> >
> > reduce the dirty_ratio, i can use memory up to 1.75GB, and then it
> will
> > call oom-killer.
> >So it helps. Are there intensive IO after reducing dirty_ratio?
>
> > > - enable vmscan trace
> > >
> > > mount -t debugfs none /sys/kernel/debug
> > > echo 1 > /sys/kernel/debug/tracing/events/vmscan/enable
> > > <eat memory and wait for crash>
> > > cat /sys/kernel/debug/tracing/trace > trace.log
> > would you like to help to see the trace.log , i add attached file.
> > There are many vmscan writes showing up in the trace.
>
> yes, the DiskIO is be not aggressive when i reduce the dirty_ratio, but
> when i use memory up to 1.75GB (total 2GB), the system suddenly crashed.
You seem to use the term "crash" for both "OOM-killed" and "kernel
panic". You mean .36 kernel will panic on memory pressure while .35
kernel will OOM kill the Xorg task?
> when i reboot and want to see the /var/log/message, it is without useful
> information.
>
> so it is other useful debug approach to find the issue?
Documentation/networking/netconsole.txt
eg. netconsole=@:/eth0,6666@10.239.51.110/00:30:48:fe:19:94
You'll need another machine to catch the panic log.
Thanks,
Fengguang
next prev parent reply other threads:[~2010-10-20 1:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 1:47 oom_killer crash linux system Figo.zhang
2010-10-18 1:57 ` KAMEZAWA Hiroyuki
2010-10-18 2:11 ` Wu Fengguang
2010-10-18 8:13 ` Figo.zhang
2010-10-18 9:10 ` KOSAKI Motohiro
2010-10-18 15:31 ` Wu Fengguang
2010-10-19 2:07 ` Figo.zhang
2010-10-19 2:59 ` KAMEZAWA Hiroyuki
2010-10-19 2:59 ` KAMEZAWA Hiroyuki
2010-10-19 5:23 ` Minchan Kim
2010-10-19 5:23 ` Minchan Kim
2010-10-19 5:26 ` KAMEZAWA Hiroyuki
2010-10-19 5:26 ` KAMEZAWA Hiroyuki
2010-10-19 5:34 ` Minchan Kim
2010-10-19 5:34 ` Minchan Kim
2010-10-20 1:35 ` Wu Fengguang
2010-10-20 1:35 ` Wu Fengguang
2010-10-20 2:06 ` Figo.zhang
2010-10-20 2:06 ` Figo.zhang
2010-10-20 2:32 ` KOSAKI Motohiro
2010-10-20 2:32 ` KOSAKI Motohiro
2010-10-20 2:58 ` Figo.zhang
2010-10-20 2:58 ` Figo.zhang
2010-10-20 3:24 ` KOSAKI Motohiro
2010-10-20 3:24 ` KOSAKI Motohiro
2010-10-20 3:43 ` Figo.zhang
2010-10-20 3:43 ` Figo.zhang
2010-10-20 5:05 ` Adam Jiang
2010-10-20 5:05 ` Adam Jiang
2010-10-19 6:22 ` KAMEZAWA Hiroyuki
2010-10-20 1:36 ` Figo.zhang
2010-10-20 1:47 ` Wu Fengguang [this message]
2010-10-19 18:43 ` David Rientjes
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=20101020014746.GA8338@localhost \
--to=fengguang.wu@intel.com \
--cc=figo1802@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.