* [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
@ 2021-03-29 9:07 Pankaj Vinodrao Joshi
2021-03-29 9:26 ` xuyang2018.jy
0 siblings, 1 reply; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-03-29 9:07 UTC (permalink / raw)
To: ltp
Hi,
I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom kernel built using Yocto but both test are getting failed repeatedly. i am not able to understand what making both test to fail since these tests are stress tests for message queue want to figure if anything going wrong with message queue.
Pasting few error message and attaching detailed logs of failures
msgstress03:-
msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call
msgstress04:-
msgstress04 0 TINFO : Found 31994 available message queues
msgstress04 0 TINFO : Using upto 2097104 pids
Fork failure in the second child of child group 9218
Fork failure in the first child of child group 9198
Fork failure in the first child of child group 9216
Fork failure in the first child of child group 9208
Fork failure in the first child of child group 9250
Fork failure in the second child of child group 9249
Fork failure in the first child of child group 9230
Fork failure in the first child of child group 9233
Fork failure in the first child of child group 9247
Fork failure in the first child of child group 9254
Fork failure in the second child of child group 9228
Fork failure in the second child of child group 9253
Fork failure in the first child of child group 9242
Fork failure in the second child of child group 9246
Fork failure in the first child of child group 9243
Fork failure in the second child of child group 9240
Fork failure in the second child of child group 9238
Fork failure in the first child of child group 9252
msgstress04 1 TFAIL : msgstress04.c:204: Fork failed (may be OK if under stress)
Fork failure in the second child of child group 9234
Kindly help to get the failure resolved.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210329/d25029eb/attachment-0001.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ms04.txt
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210329/d25029eb/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: msgs03.txt
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210329/d25029eb/attachment-0003.txt>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-03-29 9:07 [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22 Pankaj Vinodrao Joshi
@ 2021-03-29 9:26 ` xuyang2018.jy
2021-03-29 12:40 ` Pankaj Vinodrao Joshi
0 siblings, 1 reply; 11+ messages in thread
From: xuyang2018.jy @ 2021-03-29 9:26 UTC (permalink / raw)
To: ltp
Hi
Hi,
I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom kernel built using Yocto but both test are getting failed repeatedly. i am not able to understand what making both test to fail since these tests are stress tests for message queue want to figure if anything going wrong with message queue.
Pasting few error message and attaching detailed logs of failures
msgstress03:-
msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call
msgstress04:-
msgstress04 0 TINFO : Found 31994 available message queues
msgstress04 0 TINFO : Using upto 2097104 pids
Fork failure in the second child of child group 9218
For msgstress04, It is a known issue[1]. the fork fail reason see[2].
I have sent a patchset[3] to cleanup these msgstress case recently and then I will add a process num limit according to avaiable memory.
[1]https://github.com/linux-test-project/ltp/issues/509
[2]http://lists.linux.it/pipermail/ltp/2020-June/017619.html
[3]https://patchwork.ozlabs.org/project/ltp/patch/1615550541-21714-1-git-send-email-xuyang2018.jy@cn.fujitsu.com/
Fork failure in the first child of child group 9198
Fork failure in the first child of child group 9216
Fork failure in the first child of child group 9208
Fork failure in the first child of child group 9250
Fork failure in the second child of child group 9249
Fork failure in the first child of child group 9230
Fork failure in the first child of child group 9233
Fork failure in the first child of child group 9247
Fork failure in the first child of child group 9254
Fork failure in the second child of child group 9228
Fork failure in the second child of child group 9253
Fork failure in the first child of child group 9242
Fork failure in the second child of child group 9246
Fork failure in the first child of child group 9243
Fork failure in the second child of child group 9240
Fork failure in the second child of child group 9238
Fork failure in the first child of child group 9252
msgstress04 1 TFAIL : msgstress04.c:204: Fork failed (may be OK if under stress)
Fork failure in the second child of child group 9234
Kindly help to get the failure resolved.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210329/09f81b28/attachment.htm>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-03-29 9:26 ` xuyang2018.jy
@ 2021-03-29 12:40 ` Pankaj Vinodrao Joshi
2021-04-08 9:02 ` [LTP] LTP " Pankaj Vinodrao Joshi
0 siblings, 1 reply; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-03-29 12:40 UTC (permalink / raw)
To: ltp
ok..thanks..
What do you think about msgstress03, what could have went wrong ??
________________________________
From: xuyang2018.jy@fujitsu.com <xuyang2018.jy@fujitsu.com>
Sent: Monday, March 29, 2021 2:56 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Hi
Hi,
I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom kernel built using Yocto but both test are getting failed repeatedly. i am not able to understand what making both test to fail since these tests are stress tests for message queue want to figure if anything going wrong with message queue.
Pasting few error message and attaching detailed logs of failures
msgstress03:-
msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call
msgstress04:-
msgstress04 0 TINFO : Found 31994 available message queues
msgstress04 0 TINFO : Using upto 2097104 pids
Fork failure in the second child of child group 9218
For msgstress04, It is a known issue[1]. the fork fail reason see[2].
I have sent a patchset[3] to cleanup these msgstress case recently and then I will add a process num limit according to avaiable memory.
[1]https://github.com/linux-test-project/ltp/issues/509
[2]http://lists.linux.it/pipermail/ltp/2020-June/017619.html
[3]https://patchwork.ozlabs.org/project/ltp/patch/1615550541-21714-1-git-send-email-xuyang2018.jy@cn.fujitsu.com/
Fork failure in the first child of child group 9198
Fork failure in the first child of child group 9216
Fork failure in the first child of child group 9208
Fork failure in the first child of child group 9250
Fork failure in the second child of child group 9249
Fork failure in the first child of child group 9230
Fork failure in the first child of child group 9233
Fork failure in the first child of child group 9247
Fork failure in the first child of child group 9254
Fork failure in the second child of child group 9228
Fork failure in the second child of child group 9253
Fork failure in the first child of child group 9242
Fork failure in the second child of child group 9246
Fork failure in the first child of child group 9243
Fork failure in the second child of child group 9240
Fork failure in the second child of child group 9238
Fork failure in the first child of child group 9252
msgstress04 1 TFAIL : msgstress04.c:204: Fork failed (may be OK if under stress)
Fork failure in the second child of child group 9234
Kindly help to get the failure resolved.
Thanks
[EXT]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210329/92924d49/attachment.htm>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-03-29 12:40 ` Pankaj Vinodrao Joshi
@ 2021-04-08 9:02 ` Pankaj Vinodrao Joshi
2021-04-08 9:27 ` Cyril Hrubis
0 siblings, 1 reply; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-04-08 9:02 UTC (permalink / raw)
To: ltp
Hi,
I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom kernel built using Yocto but both test are getting failed repeatedly. i am not able to understand what making both test to fail since these tests are stress tests for message queue want to figure if anything going wrong with message queue.
Pasting few error messages and attaching detailed logs of failures
msgstress03:-
msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call
Kindly help to get the failure resolved.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210408/25be34a2/attachment.htm>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-04-08 9:02 ` [LTP] LTP " Pankaj Vinodrao Joshi
@ 2021-04-08 9:27 ` Cyril Hrubis
2021-04-08 9:38 ` Pankaj Vinodrao Joshi
0 siblings, 1 reply; 11+ messages in thread
From: Cyril Hrubis @ 2021-04-08 9:27 UTC (permalink / raw)
To: ltp
Hi!
> I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom
> kernel built using Yocto but both test are getting failed repeatedly.
> i am not able to understand what making both test to fail since these
> tests are stress tests for message queue want to figure if anything
> going wrong with message queue.
What about the LTP version? Can you please include that information
every time you ask abou test failures?
> Pasting few error messages and attaching detailed logs of failures
>
> msgstress03:-
> msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
> msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call
This looks like fallout from the test doing unclean exit, the root cause
for the failure should be somewhere at the beginning of the log.
--
Cyril Hrubis
chrubis@suse.cz
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-04-08 9:27 ` Cyril Hrubis
@ 2021-04-08 9:38 ` Pankaj Vinodrao Joshi
2021-04-08 10:28 ` Cyril Hrubis
0 siblings, 1 reply; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-04-08 9:38 UTC (permalink / raw)
To: ltp
sorry, i forgot to attach log file.The LTP version i am using is LTP Version: 20200515 and even i have tried with latest master sources as well
Thanks
________________________________
From: Cyril Hrubis <chrubis@suse.cz>
Sent: Thursday, April 8, 2021 2:57 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Hi!
> I am running msgstress03,msgstress04 with 5.10.19 and 5.10.22 custom
> kernel built using Yocto but both test are getting failed repeatedly.
> i am not able to understand what making both test to fail since these
> tests are stress tests for message queue want to figure if anything
> going wrong with message queue.
What about the LTP version? Can you please include that information
every time you ask abou test failures?
> Pasting few error messages and attaching detailed logs of failures
>
> msgstress03:-
> msgsnd() error in child 9458, write # = 10000, key = 65e2d9c4: Interrupted system call
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43902).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43925).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43927).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: Cannot open directory /tmp/ltp-9Raz9tykpq/msgQaAD8i; errno=2: ENOENT
> msgsnd() error in child 9468, write # = 10000, key = 5364a4ac: Interrupted system call
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43918).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgsnd() error in child 9450, write # = 10000, key = 6015ef48: Interrupted system call
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43883).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgstress03 1 TBROK : tst_sig.c:232: unexpected signal SIGINT(2) received (pid = 43924).
> msgstress03 2 TBROK : tst_sig.c:232: Remaining cases broken
> msgstress03 0 TWARN : tst_tmpdir.c:336: tst_rmdir: rmobj(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed: unlink(/tmp/ltp-9Raz9tykpq/msgQaAD8i) failed; errno=2: ENOENT
> msgsnd() error in child 9454, write # = 10000, key = 37efb13a: Interrupted system call
This looks like fallout from the test doing unclean exit, the root cause
for the failure should be somewhere at the beginning of the log.
--
Cyril Hrubis
chrubis@suse.cz
[EXT]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210408/68863712/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: msgstress03
Type: application/octet-stream
Size: 56955 bytes
Desc: msgstress03
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210408/68863712/attachment-0001.obj>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-04-08 9:38 ` Pankaj Vinodrao Joshi
@ 2021-04-08 10:28 ` Cyril Hrubis
2021-04-12 5:18 ` Pankaj Vinodrao Joshi
0 siblings, 1 reply; 11+ messages in thread
From: Cyril Hrubis @ 2021-04-08 10:28 UTC (permalink / raw)
To: ltp
Hi!
> sorry, i forgot to attach log file.The LTP version i am using is LTP Version: 20200515 and even i have tried with latest master sources as well
Using anything older than the latest stable release is strongly discouraged.
<<<test_start>>>
tag=msgstress03 stime=1617104557
cmdline="msgstress03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
msgstress03 1 TFAIL : msgstress03.c:155: Fork failed (may be OK if under stress)
<<<execution_status>>>
Here is the real reason for the failures, the test fails to fork() a few times,
that is since the machine seems to have 8GB RAM and for the default maximal
number of message queues 32000 (as set in /proc/sys/kernel/msgmni) is too high.
In other words we do have 8GB RAM and try to fork 64000 (two processes per
message queue) that leaves us about 125kB per process (aprox: 8 * 1024 * 1024 /
64000) which is likely too low. You can try to set the /proc/sys/kernel/msgmni
to half of it's default i.e. 16000 and re-run the test.
The test should be cleaned up changed to scale better with available memory
however estimating how much memory will the test process need is not an easy
task.
The rest of the messages you see are as I've said fallout from the test doing
unclean exit, i.e. the main process exits without waiting for it's children.
Which should be fixed as well, when the test is being rewritten.
--
Cyril Hrubis
chrubis@suse.cz
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-04-08 10:28 ` Cyril Hrubis
@ 2021-04-12 5:18 ` Pankaj Vinodrao Joshi
2021-04-12 11:28 ` Cyril Hrubis
0 siblings, 1 reply; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-04-12 5:18 UTC (permalink / raw)
To: ltp
Hi Cyril,
Thanks for your response and help for understanding the reason of testcase failure
I too running the test on the machine with 8GB of RAM and the value for the msgmmni is 32000 by default and i have changed 16000 then also i am not able to see any diff in output.
Anything else that i can try ??
Thanks
________________________________
From: Cyril Hrubis <chrubis@suse.cz>
Sent: Thursday, April 8, 2021 3:58 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Hi!
> sorry, i forgot to attach log file.The LTP version i am using is LTP Version: 20200515 and even i have tried with latest master sources as well
Using anything older than the latest stable release is strongly discouraged.
<<<test_start>>>
tag=msgstress03 stime=1617104557
cmdline="msgstress03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
Fork failed (may be OK if under stress)
msgstress03 1 TFAIL : msgstress03.c:155: Fork failed (may be OK if under stress)
<<<execution_status>>>
Here is the real reason for the failures, the test fails to fork() a few times,
that is since the machine seems to have 8GB RAM and for the default maximal
number of message queues 32000 (as set in /proc/sys/kernel/msgmni) is too high.
In other words we do have 8GB RAM and try to fork 64000 (two processes per
message queue) that leaves us about 125kB per process (aprox: 8 * 1024 * 1024 /
64000) which is likely too low. You can try to set the /proc/sys/kernel/msgmni
to half of it's default i.e. 16000 and re-run the test.
The test should be cleaned up changed to scale better with available memory
however estimating how much memory will the test process need is not an easy
task.
The rest of the messages you see are as I've said fallout from the test doing
unclean exit, i.e. the main process exits without waiting for it's children.
Which should be fixed as well, when the test is being rewritten.
--
Cyril Hrubis
chrubis@suse.cz
[EXT]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210412/845c8a52/attachment.htm>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-04-12 5:18 ` Pankaj Vinodrao Joshi
@ 2021-04-12 11:28 ` Cyril Hrubis
2021-05-17 7:41 ` Pankaj Vinodrao Joshi
0 siblings, 1 reply; 11+ messages in thread
From: Cyril Hrubis @ 2021-04-12 11:28 UTC (permalink / raw)
To: ltp
Hi!
> Thanks for your response and help for understanding the reason of testcase failure
> I too running the test on the machine with 8GB of RAM and the value for the msgmmni is 32000 by default and i have changed 16000 then also i am not able to see any diff in output.
>
> Anything else that i can try ??
Try with less, I suppose 8000 should work fine.
If estimating how many processes we can run was easy the test would have
been fixed a long time ago.
--
Cyril Hrubis
chrubis@suse.cz
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-04-12 11:28 ` Cyril Hrubis
@ 2021-05-17 7:41 ` Pankaj Vinodrao Joshi
2021-05-18 7:23 ` Pankaj Vinodrao Joshi
0 siblings, 1 reply; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-05-17 7:41 UTC (permalink / raw)
To: ltp
Hi Cyril,
With value of msgmni 8000 it worked well for me but i want to understand which part from the log (produced by strace or some other method) i should be focused on to get to know ohkk it is failure because of value of msgmni is more.
How you analyzed and helped me to fix ,what approach you have followed ?
Thanks
________________________________
From: Cyril Hrubis <chrubis@suse.cz>
Sent: Monday, April 12, 2021 4:58 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Hi!
> Thanks for your response and help for understanding the reason of testcase failure
> I too running the test on the machine with 8GB of RAM and the value for the msgmmni is 32000 by default and i have changed 16000 then also i am not able to see any diff in output.
>
> Anything else that i can try ??
Try with less, I suppose 8000 should work fine.
If estimating how many processes we can run was easy the test would have
been fixed a long time ago.
--
Cyril Hrubis
chrubis@suse.cz
[EXT]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210517/625be27b/attachment.htm>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
2021-05-17 7:41 ` Pankaj Vinodrao Joshi
@ 2021-05-18 7:23 ` Pankaj Vinodrao Joshi
0 siblings, 0 replies; 11+ messages in thread
From: Pankaj Vinodrao Joshi @ 2021-05-18 7:23 UTC (permalink / raw)
To: ltp
Kind reminder. Please help me with approaches.
Thanks
________________________________
From: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Sent: Monday, May 17, 2021 1:11 PM
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Hi Cyril,
With value of msgmni 8000 it worked well for me but i want to understand which part from the log (produced by strace or some other method) i should be focused on to get to know ohkk it is failure because of value of msgmni is more.
How you analyzed and helped me to fix ,what approach you have followed ?
Thanks
________________________________
From: Cyril Hrubis <chrubis@suse.cz>
Sent: Monday, April 12, 2021 4:58 PM
To: Pankaj Vinodrao Joshi <Pankaj.VJ@exaleapsemi.com>
Cc: ltp@lists.linux.it <ltp@lists.linux.it>
Subject: Re: [LTP] LTP msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22
Hi!
> Thanks for your response and help for understanding the reason of testcase failure
> I too running the test on the machine with 8GB of RAM and the value for the msgmmni is 32000 by default and i have changed 16000 then also i am not able to see any diff in output.
>
> Anything else that i can try ??
Try with less, I suppose 8000 should work fine.
If estimating how many processes we can run was easy the test would have
been fixed a long time ago.
--
Cyril Hrubis
chrubis@suse.cz
[EXT]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210518/5757494f/attachment.htm>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2021-05-18 7:23 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-29 9:07 [LTP] msgstress03, msgstress04 failure on linux 5.10.19 and 5.10.22 Pankaj Vinodrao Joshi
2021-03-29 9:26 ` xuyang2018.jy
2021-03-29 12:40 ` Pankaj Vinodrao Joshi
2021-04-08 9:02 ` [LTP] LTP " Pankaj Vinodrao Joshi
2021-04-08 9:27 ` Cyril Hrubis
2021-04-08 9:38 ` Pankaj Vinodrao Joshi
2021-04-08 10:28 ` Cyril Hrubis
2021-04-12 5:18 ` Pankaj Vinodrao Joshi
2021-04-12 11:28 ` Cyril Hrubis
2021-05-17 7:41 ` Pankaj Vinodrao Joshi
2021-05-18 7:23 ` Pankaj Vinodrao Joshi
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.