From: Cyril Hrubis <chrubis@suse.cz>
To: Troy-lee <798528972@qq.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Could you help me to analyse the LTP output
Date: Mon, 15 Dec 2014 11:49:09 +0100 [thread overview]
Message-ID: <20141215104908.GA19679@rei.suse.de> (raw)
In-Reply-To: <tencent_35471B31762F345622E4EC71@qq.com>
Hi!
> The kernel version is 3.1.0, and the LTP version is 201408128.There
> are some info from screen output, maybe can help us to analyse us to
> analyse what error is going on.And I am learning the ltp test, could
> you provide some primer.
The log shows that the kernel is out of memory and that oom killer
terminates all processes in order to get some free RAM.
How much memory has this system? The readahead02 testcase maps, by
default, 64MB file into memory. If there is not enough, the test should
either be disabled changed to use less (the -s parameter).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-12-15 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 0:44 [LTP] Could you help me to analyse the LTP output =?gb18030?B?VHJveS1sZWU=?=
2014-12-09 13:04 ` Cyril Hrubis
2014-12-09 13:09 ` Cyril Hrubis
2014-12-09 13:45 ` Cyril Hrubis
2014-12-13 7:42 ` =?gb18030?B?VHJveS1sZWU=?=
2014-12-15 10:49 ` Cyril Hrubis [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=20141215104908.GA19679@rei.suse.de \
--to=chrubis@suse.cz \
--cc=798528972@qq.com \
--cc=ltp-list@lists.sourceforge.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