From: Peter Soetens <peter.soetens@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [FIX] Summary: Xenomai 2.3.2 and 2.4 lock-ups and OOPSes
Date: Mon, 17 Sep 2007 14:55:49 +0200 [thread overview]
Message-ID: <200709171455.49748.peter.soetens@domain.hid> (raw)
In-Reply-To: <1189882379.25006.181.camel@domain.hid>
On Saturday 15 September 2007 20:52:59 Philippe Gerum wrote:
> On Fri, 2007-09-07 at 11:27 +0200, Peter Soetens wrote:
> > Just in case you hooked off the long discussion about the issues we found
> > from Xenomai 2.3.2 on:
> >
> > o We are using the xeno_native skin, create Xeno tasks and semaphores,
> > but have strong indications that the crashes are caused by the memory
> > allocation scheme of Xenomai in combination with task creation/deletion
> > o We found two ways to break Xenomai, causing a 'Killed'
> > (rt_task_delete) and causing an OOPS (rt_task_join).
> > o They happen on 2.6.20 and 2.6.22 kernels
> > o On the 2.3 branch, r2429 works, r2433 causes the faults. The patch is
> > small, and in the ChangLog:
>
> Please try this patch against v2.3.x. A double free issue on a task TCB
> already scheduled for memory release was causing all sorts of troubles,
> basically trashing the system heap afterwards:
Thanks, we'll try, test and report ASAP (= somewhere this week.)
Peter
--
Peter Soetens -- FMTC -- <http://www.fmtc.be>
next prev parent reply other threads:[~2007-09-17 12:55 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
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 [this message]
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=200709171455.49748.peter.soetens@domain.hid \
--to=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.