From: Zhouping Liu <zliu@redhat.com>
To: "Lukáš Doktor" <ldoktor@redhat.com>
Cc: ltp-list@lists.sourceforge.net, Cleber Rosa <crosa@redhat.com>
Subject: Re: [LTP] Broken kernel/mem/ksm01 test
Date: Fri, 27 Jul 2012 07:15:49 -0400 (EDT) [thread overview]
Message-ID: <36213450.4314745.1343387749585.JavaMail.root@redhat.com> (raw)
In-Reply-To: <500952EC.6050504@redhat.com>
----- Original Message -----
> From: "Lukáš Doktor" <ldoktor@redhat.com>
> To: ltp-list@lists.sourceforge.net, "Cleber Rosa" <crosa@redhat.com>, vlee@twitter.com
> Sent: Friday, July 20, 2012 8:45:32 PM
> Subject: [LTP] Broken kernel/mem/ksm01 test
>
> Hi guys,
>
> I'm testing LTP-20120614 on Fedora 17 and it always stuck on ksm01
> test.
I guess ksm service(user space) is on, which will set
/sys/kernel/mm/ksm/run to 0, then full_scans will stop to count,
this lead to the process(ksm01) stay in the following 'while()' all the time.
while (new_num < old_num * 3) {
sleep(1);
read_file(PATH_KSM "full_scans", buf);
new_num = SAFE_STRTOL(cleanup, buf, 0, LONG_MAX);
}
that's why the testing stuck on ksm01.
so you need to stop ksm service:
# systemctl stop ksm.service
after the ksm.service is stopped, I'm sure ksm01 can finish its job at least.
also the ksm0* cases have some error[1], the latest version has fixed them.
I suggest you use git version, which includes the fix(commit 60c41a5465cc5)
[1] http://sourceforge.net/mailarchive/message.php?msg_id=29088640
>
> I went through sources and the problem is I have KSM already enabled
> so
> the full_scans is a huge number. The function _group_check waits till
> KSM does 3 * full_scans which in my case never ends (well it might
> finish in a couple of years).
>
> To me it doesn't even make sense to wait 3 * full_scans as in the
> first
> check it waits 1-2 seconds, in second check it waits few seconds and
> it
> keeps growing further you goes.
>
> Would you please take look on this issue? I'd really appreciate it.
>
> Kind regards,
> Lukáš Doktor
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions
> will include endpoint security, mobile security and the latest in
> malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
--
Thanks,
Zhouping
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-07-27 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 12:45 [LTP] Broken kernel/mem/ksm01 test Lukáš Doktor
2012-07-20 13:06 ` Lukáš Doktor
2012-07-27 8:45 ` Caspar Zhang
2012-07-27 11:15 ` Zhouping Liu [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=36213450.4314745.1343387749585.JavaMail.root@redhat.com \
--to=zliu@redhat.com \
--cc=crosa@redhat.com \
--cc=ldoktor@redhat.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