public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Shubham Goyal <shubham@linux.vnet.ibm.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP: memcg_stress_test hanging whole box
Date: Fri, 02 Dec 2011 23:00:04 +0530	[thread overview]
Message-ID: <4ED90B1C.8000204@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111129220308.GA3953@nik-comp.lan>

On Wednesday 30 November 2011 03:33 AM, Nikola Ciprich wrote:
> Hello Shubham,
>
> I tried setting swap to 8GB, but the result is the same... the box gets into state
> that I can't login to it even after few hours, so hard reset is needed..
> When I have top started, I see a lot of memcg_process_stress processes.
> What is strange, when I start the test with swap disabled, memcg_process_stress processes
> just seem to eat all physical memory and then just sleep. OOM killer doesn't kill anything,
> but the box doesn't hang..
> weird..
> I'm wondering whether to report this to kernel list?
> or do You have any idea on where to look?
> cheers
> nik

Hi Nikola,

What I recently noticed was the controller test hang problem is coming 
with old versions of LTP. I tried with latest release of LTP on the same 
affected machine and I did not observed any test case or system hang. I 
hope you are using latest LTP downloaded from 'ltp.sourceforge.net'?

There might be a issue with oom that it is not able to kill the memory 
intensive process but you need to gather more information about the 
hanging process first. You might want to run only the hanging test i.e. 
memcg_stress and not complete LTP to narrow down the issue. Just check 
whether you are able to reproduce the issue when only memcg_stress test 
is running There are chances that test case itself has some issues.

Thanks,
Shubham



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2011-12-02 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27 20:12 [LTP] LTP: memcg_stress_test hanging whole box Nikola Ciprich
2011-11-29  6:50 ` Shubham Goyal
2011-11-29 22:03   ` Nikola Ciprich
2011-12-02 17:30     ` Shubham Goyal [this message]
2011-12-05 12:01       ` Nikola Ciprich
2011-12-06 10:46         ` Shubham Goyal

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=4ED90B1C.8000204@linux.vnet.ibm.com \
    --to=shubham@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=nikola.ciprich@linuxbox.cz \
    /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