All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Ronny Meeus <ronny.meeus@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai-forge: thread using 100% cpu load
Date: Thu, 07 Mar 2013 16:56:52 +0100	[thread overview]
Message-ID: <5138B8C4.3000708@xenomai.org> (raw)
In-Reply-To: <51386CB1.6090701@xenomai.org>

On 03/07/2013 11:32 AM, Philippe Gerum wrote:
> On 03/07/2013 11:02 AM, Ronny Meeus wrote:
>>
>> thanks for the patch.
>> With this patch the test application is working fine, no cpuload is
>> observed anymore.
>> Our real application on the other hand aborts after some time with
>> this reporting:
>> ------------------------------------------------------------------------------
>>
>> [ ERROR BACKTRACE: thread root ]
>>
>>     #0  EAGAIN in t_create(), task.c:320
>>     #1  EAGAIN in copperplate_create_thread(), internal.c:138
>> ------------------------------------------------------------------------------
>>
>>
>> I did not observe this when running with the xenomai before the patch.
>> Do you have a clue about why I see this?
>>
>>
>
> There is likely a resource leakage hiding somewhere. I'll have a look.
>

After hours running the test case, I didn't see any sign of leakage, 
same after code inspection. Maybe this bug is visible now that your app 
can run more code. There are several potential causes for EAGAIN, 
however assuming this is not a rlimit issue, checking /proc/vmstat while 
your app runs may give some hint.

-- 
Philippe.


  reply	other threads:[~2013-03-07 15:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 19:19 [Xenomai] Xenomai-forge: thread using 100% cpu load Ronny Meeus
2013-02-28 20:10 ` Gilles Chanteperdrix
2013-02-28 20:22   ` Thomas De Schampheleire
2013-02-28 20:27     ` Gilles Chanteperdrix
2013-03-01  8:22     ` Philippe Gerum
2013-03-01  8:26       ` Gilles Chanteperdrix
2013-03-01  8:30         ` Philippe Gerum
2013-03-01  8:30           ` Gilles Chanteperdrix
2013-03-01  8:41             ` Philippe Gerum
2013-03-02 11:13               ` Ronny Meeus
2013-03-05 12:43                 ` Ronny Meeus
2013-03-05 13:28                   ` Philippe Gerum
2013-03-05 14:08                   ` Philippe Gerum
2013-03-05 14:25                     ` Ronny Meeus
2013-03-05 14:47                       ` Philippe Gerum
2013-03-05 14:53                         ` Ronny Meeus
2013-03-06 10:55                     ` Ronny Meeus
2013-03-06 11:09                       ` Philippe Gerum
2013-03-06 11:18                         ` Philippe Gerum
2013-03-06 13:24                       ` Philippe Gerum
2013-03-06 13:49                 ` Philippe Gerum
2013-03-06 14:32                   ` Ronny Meeus
2013-03-06 15:49                     ` Philippe Gerum
2013-03-07 10:02                       ` Ronny Meeus
2013-03-07 10:32                         ` Philippe Gerum
2013-03-07 15:56                           ` Philippe Gerum [this message]
2013-03-07 19:51                             ` Ronny Meeus
2013-03-08  7:44                               ` Ronny Meeus
2013-02-28 20:30   ` Ronny Meeus
2013-02-28 20:35     ` Gilles Chanteperdrix

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=5138B8C4.3000708@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=ronny.meeus@gmail.com \
    --cc=xenomai@xenomai.org \
    /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.