From: Philippe Gerum <rpm@xenomai.org>
To: Peter Soetens <peter.soetens@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Summary: Xenomai 2.3.2 and 2.4 lock-ups and OOPSes
Date: Thu, 13 Sep 2007 14:49:35 +0200 [thread overview]
Message-ID: <1189687775.25006.63.camel@domain.hid> (raw)
In-Reply-To: <200709131006.52248.peter.soetens@domain.hid>
On Thu, 2007-09-13 at 10:06 +0200, Peter Soetens wrote:
> >
> > Please point me at the actual Orocos test code that breaks, with the
> > hope to get a fairly standalone test case from it; if you do have a
> > standalone test case already, this would be even better. I intend to
> > address this issue asap.
>
> I stripped the OS layer of Orocos for xenomai and built a testcase, which
> causes a complete lockup with that. In order to avoid the lock-up, comment
> some thread/mutex/semaphore creations. All these classes call the functions
> from fosi.c and fosi_internal_join.cpp. So the testcase could be reduced to
> call only these functions...
> It seems you need to construct a number of threads and mutexes in the
> same application before it happens. With only 'little' use of these
> primitives, our applications run fine 1000's times in a row.
Ok. I can confirm that something tragically bugous is happening at
nucleus level when running this testcase. So far, I already triggered
the -ENOMEM issue, and a nifty crash during task creation. I'll dig
this, thanks.
--
Philippe.
next prev parent reply other threads:[~2007-09-13 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 9:27 [Xenomai-core] Summary: Xenomai 2.3.2 and 2.4 lock-ups and OOPSes Peter Soetens
2007-09-07 12:46 ` Philippe Gerum
2007-09-07 18:53 ` Gilles Chanteperdrix
2007-09-07 19:07 ` Gilles Chanteperdrix
2007-09-13 8:06 ` Peter Soetens
2007-09-13 8:22 ` Peter Soetens
2007-09-13 12:49 ` Philippe Gerum [this message]
2007-09-15 18:52 ` [Xenomai-core] [FIX] " Philippe Gerum
2007-09-16 17:49 ` Gilles Chanteperdrix
2007-09-16 19:31 ` Philippe Gerum
2007-09-17 12:55 ` Peter Soetens
2007-09-17 13:59 ` Peter Soetens
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=1189687775.25006.63.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=peter.soetens@domain.hid \
--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.