All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [BUG] scheduling order of dying shadow threads
Date: Tue, 08 Nov 2005 16:51:02 +0100	[thread overview]
Message-ID: <4370C966.3030903@domain.hid> (raw)
In-Reply-To: <4370641D.7010906@domain.hid>

Jan Kiszka wrote:
> Hi Philippe,
> 
> I think this one is for you: ;)
> 
> Sebastian got almost mad with his CAN driver while tracing a strange
> scheduling behaviour during shadow thread deletion for several days(!) -
> and I was right on the way to follow him yesterday evening. Attached is
> a simplified demonstration of the effect, consisting of a RTDM driver
> and both a kernel and user space application to trigger it.
> 

I've spotted the issue in nucleus/shadow.c. Basically, the root thread priority 
boost was leaking to a non-shadow thread due to a missing priority reset in the 
lostage APC handler, whilst a shadow was in the process of relaxing. Really 
funky bug, thanks! :o> Fixed in the repo hopefully for good. The scheduling 
sequence is now correct with your demo app on my box.

-- 

Philippe.


  parent reply	other threads:[~2005-11-08 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08  8:38 [Xenomai-core] [BUG] scheduling order of dying shadow threads Jan Kiszka
2005-11-08  9:32 ` Philippe Gerum
2005-11-08 15:51 ` Philippe Gerum [this message]
2005-11-08 16:21   ` Sebastian Smolorz
2005-11-08 16:30   ` Jan Kiszka
2005-11-08 17:47     ` Philippe Gerum
2005-11-14 12:45       ` [Xenomai-core] [BUG] rt_pipe_flush declaration missing in skins/native/pipe.h Ignacio García Pérez
2005-11-14 15:02         ` Philippe Gerum
2005-11-14 16:08           ` Ignacio García Pérez
2005-11-14 16:20             ` Philippe Gerum

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=4370C966.3030903@domain.hid \
    --to=rpm@xenomai.org \
    --cc=kiszka@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.