From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Scheduling while atomic
Date: Wed, 18 Jan 2006 10:18:04 +0100 [thread overview]
Message-ID: <17358.1996.293519.413160@domain.hid> (raw)
In-Reply-To: <fd6a47a90601171559x13acf2c2m@domain.hid>
Jeroen Van den Keybus wrote:
> Gilles,
>
>
> I cannot reproduce those messages after turning nucleus debugging on.
> Instead, I now either get relatively more failing mutexes or even hard
> lockups with the test program I sent to you. If the computer didn't crash,
> dmesg contains 3 Xenomai messages relating to a task being movend to
> secondary domain after exception #14. As when the computer crashes: I have
> written the last kernel panic message on a paper. Please tell if you want
> also the addresses or (part of) the call stack.
Could you try adding a call to mlockall(MCL_CURRENT|MCL_FUTURE) ?
Also note that you do not need protecting accesses to file descriptor
with rt_mutexes. stdio file descriptor are protected with pthread
mutexes, and pthread mutexes functions cause threads migration to
secondary mode. And unix file descriptor are passed to system calls,
which also cause migration to secondary mode.
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-01-18 9:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 23:59 [Xenomai-core] Scheduling while atomic Jeroen Van den Keybus
2006-01-18 9:18 ` Gilles Chanteperdrix [this message]
2006-01-18 20:06 ` Jan Kiszka
2006-01-18 20:14 ` Jan Kiszka
2006-01-18 20:25 ` Jan Kiszka
2006-01-29 23:28 ` Philippe Gerum
2006-01-18 20:21 ` Gilles Chanteperdrix
2006-01-18 20:26 ` Gilles Chanteperdrix
2006-01-18 20:30 ` Jan Kiszka
2006-01-18 20:46 ` Jan Kiszka
[not found] ` <fd6a47a90601181236u5a482ba5q@domain.hid>
[not found] ` <43CEA7AC.9080300@domain.hid>
[not found] ` <fd6a47a90601181254s11edbb28l@domain.hid>
[not found] ` <43CEADBE.4040802@domain.hid>
2006-01-18 21:11 ` Jeroen Van den Keybus
2006-01-18 21:16 ` Jan Kiszka
2006-01-18 21:39 ` Jeroen Van den Keybus
2006-01-18 23:49 ` Jeroen Van den Keybus
2006-01-18 23:51 ` Jeroen Van den Keybus
2006-01-19 10:10 ` Jeroen Van den Keybus
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 20:04 Jeroen Van den Keybus
2006-01-18 20:20 ` Hannes Mayer
2006-01-18 21:12 ` Jan Kiszka
2006-01-18 21:26 ` Hannes Mayer
[not found] ` <fd6a47a90601181334y14b06d6an@domain.hid>
2006-01-18 22:13 ` Hannes Mayer
2006-01-18 22:26 ` Jeroen Van den Keybus
2006-01-18 22:17 ` Jeroen Van den Keybus
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=17358.1996.293519.413160@domain.hid \
--to=gilles.chanteperdrix@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.