Philippe Gerum wrote: > On Tue, 2007-02-13 at 15:28 +0100, Jan Kiszka wrote: >> Philippe Gerum wrote: >>> On Tue, 2007-02-13 at 15:07 +0100, Jan Kiszka wrote: >>>> Stephan Zimmermann wrote: >>>>> I wasn't able to isolate the section of my code that causes the crash by >>>>> now. The only thing I figured out by now is that the particular crash >>>>> does not happen with 2.3.x rev 2077. >>>>> So I guess some change from 2077 to the 2139 revision did break something. >>>> Could you track the issue a bit more down? There are not to many >>>> "interesting" changes to 2.3.x. A few milestones I found in the ChangeLog: >>>> >>>> - 2092: Allow sleeping scheduler locks >>>> - 2108: Before RPI rework >>>> >>>> Anything after 2108 only makes sense to dissect when you switch on >>> s,on,off, >> Nope. If this switch is off, RPI is enabled while known to be buggy, right? >> > > Btw, RPI was not buggy so so that it could cause crashes; it was failing > to _always_ keep a thread's priority consistent across domain migration, > which is quite different. IOW, do not start switching on RPIDISABLE > blindly when your box goes south, it's most likely unrelated to what has > been fixed recently.
Well, I recalled some temporary locking changes on RPI somewhere in this period. My feeling was to better exclude their potential side-effects from the testing rounds.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
