All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mariusz Janiak" <mariuszjaniak@wp.pl>
To: peter@thesourceworks.com
Cc: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] Odp: Re:  SIGXCPU with rt_mutex_release
Date: Mon, 31 Dec 2012 20:14:20 +0100	[thread overview]
Message-ID: <50e1e40c413df8.28309699@wp.pl> (raw)

Thank you Gilles, I my opinion Peter is right that we should start debuging from OROCOS side. If it will be Xenomai issue I will let you know. 

Mariusz

PS. Orocos related topic is following 

http://www.orocos.org/forum/orocos/orocos-users/orocos-26-xenomai-262-and-sigxcpu-cpu-time-limit-exceeded

 
Dnia Poniedziałek, 31 Grudnia 2012 18:52 Peter Soetens <peter@thesourceworks.com> napisał(a)
> Hi all,
> Thanks for the analysis. I'd propose to move this to bugs.orocos.org where we can try to reproduce and track this bug in orocos.
> We've been testing in our buildfarm against xenomai 2.5, so this might be something we did not notice until now...
> Peter
> Op maandag 31 december 2012 schreef Gilles Chanteperdrix (gilles.chanteperdrix@xenomai.org) het volgende:
> > On 12/31/2012 06:32 PM, Mariusz Janiak wrote:
> >  
> >  > Hi,
> >  >
> >  > I have met problem when I run OROCOS helloWord example. Xenomai
> >  > generate SIGXCPU signal when rt_mutex_release(...) is called. I have
> >  > installed signal handler for each realtime thread created by OROCOS
> >  > and I get following result
> >  >
> >  > SIGDEBUG received, reason 4: affected by priority inversion
> >  
> >  
> >  There is a problem in your application, namely a mutex owned by a thread
> >  running with the SCHED_OTHER scheduling policy, released while Xenomai
> >  did not notice that the same thread had taken the mutex. This could
> >  happen if for instance you change the scheduling policy while holding a
> >  mutex.
> >  
> >  Please try reducing the error to a simple testcase which will allow us
> >  to investigate this issue.
> >  
> >  > There is much bigger mess during exiting from application. I am not
> >  > pretty sure this is a Xenomai problem, if not sorry for bothering. I
> >  > haven check it with previous Xenomai release yet.
> >  
> >  
> >  We need facts to start working, again, please write a simple test case
> >  to help investigating the issue.
> >  
> >  --
> >                                                                  Gilles.
> >  
> >  _______________________________________________
> >  Xenomai mailing list
> >  Xenomai@xenomai.org
> >  http://www.xenomai.org/mailman/listinfo/xenomai


 





                 reply	other threads:[~2012-12-31 19:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50e1e40c413df8.28309699@wp.pl \
    --to=mariuszjaniak@wp.pl \
    --cc=peter@thesourceworks.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.