All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] fata: removing non-linked element...
Date: Tue, 13 Feb 2007 19:17:39 +0100	[thread overview]
Message-ID: <45D200C3.1030001@domain.hid> (raw)
In-Reply-To: <1171385716.885.17.camel@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

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.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-02-13 18:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 12:12 [Xenomai-help] fata: removing non-linked element Stephan Zimmermann
2007-02-09 12:28 ` Jan Kiszka
2007-02-09 14:04   ` Stephan Zimmermann
2007-02-13 13:36   ` Stephan Zimmermann
2007-02-13 13:42   ` Stephan Zimmermann
2007-02-13 14:07     ` Jan Kiszka
2007-02-13 14:25       ` Philippe Gerum
2007-02-13 14:28         ` Jan Kiszka
2007-02-13 14:47           ` Philippe Gerum
2007-02-13 16:55           ` Philippe Gerum
2007-02-13 18:17             ` Jan Kiszka [this message]
2007-02-13 18:58               ` Philippe Gerum
2007-02-16 12:12                 ` Stephan Zimmermann
2007-02-16 17:06                   ` Jan Kiszka
2007-02-16 17:58                     ` Jan Kiszka
2007-02-16 18:15                       ` Philippe Gerum
2007-02-16 18:25                         ` Jan Kiszka
2007-02-16 18:34                           ` Philippe Gerum
2007-02-16 18:38                             ` Jan Kiszka
2007-02-16 18:47                               ` Philippe Gerum
2007-02-22 13:27                                 ` Stephan Zimmermann
2007-02-22 13:50                                   ` Jan Kiszka
2007-02-22 15:49                                     ` Stephan Zimmermann
2007-02-16 17:11                   ` Jan Kiszka
2007-02-09 13:44 ` Gilles Chanteperdrix
2007-02-09 14:08   ` Stephan Zimmermann

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=45D200C3.1030001@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpm@xenomai.org \
    --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.