From: Romu Hu <huruomu@gmail.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] msgctl11 TBROK Not enough free pids
Date: Tue, 27 Sep 2011 20:38:22 +0800 [thread overview]
Message-ID: <4E81C3BE.7000004@gmail.com> (raw)
In-Reply-To: <4E81A27B.7030908@casparzhang.com>
On 2011/9/27 18:16, Caspar Zhang wrote:
> On 09/26/2011 10:21 PM, Romu Hu wrote:
>> Hi,
>>
>> msgctl11 in ltp-20110915 failed on 2.6.39 kernel:
>>
>> msgctl11 1 TBROK : Not enough free pids
>>
>> I found that before error out,
>>
>> MSGMNI is 32768
>> MAXNKIDS is 10
>> free_pids is 32611
>> maxnkids = ((free_pids / 4) / MSGMNI);
>> so maxnkids is zero, which is why msgctl11 failed.
>>
>> Is this problem of testcase or problem of the tested system?
>>
>> Thanks
>>
>
> I think it's a configuration issue.
>
> Cyril, do you think is it better to change TBROK to TCONF here?
>
> - tst_resm(TBROK, "Not enough free pids");
> + tst_resm(TCONF, "Not enough free pids");
>
> Thanks,
> Caspar
I changed MSGMNI in /proc to below 3000 and test passed.
Thanks
--
Regards,
Romu
------------------------------------------------------------------------------
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. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2011-09-27 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 14:21 [LTP] msgctl11 TBROK Not enough free pids Romu Hu
[not found] ` <4E81A27B.7030908@casparzhang.com>
2011-09-27 12:38 ` Romu Hu [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=4E81C3BE.7000004@gmail.com \
--to=huruomu@gmail.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 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.