From: Steve Kreyer <steve.kreyer@domain.hid>
To: Bernhard Walle <Bernhard.Walle@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Re: Timer problems?
Date: Sat, 26 Aug 2006 23:23:03 +0200 [thread overview]
Message-ID: <44F0BBB7.7030703@domain.hid> (raw)
In-Reply-To: <slrneeuefr.v1d.Bernhard.Walle@domain.hid>
Hi Bernhard, :)
Bernhard Walle wrote:
> Hello,
>
> first of all: you replied to a previous mail which results in a broken
> thread three in the mail client ... Pleaes create new mail for new
> requests.
> The example you've provided exits immediately here because you don't
> wait in the main() function.
>
Yes, Iam aware of this, but in fact the waiting via pause or sleep in
the Linux process (main function)
failed and results in a system lock up.
> I modified your example to work:
> http://pastie.caboo.se/10259
>
The trick of calling rt_task_join instead of doing a pause is a nice
idea, but it doesn't solve my problem fully(see below*).
>
> No problem here, for example I call sleep(2) in the RT thread and it
> work.
It is not my concern to call a standard linux function in the RT task.
> Calling Linux functions in RT code should work in Xenomai,
> although it's not hard realtime safe any more because the thread gets
> switched to the Linux scheduler.
>
*The reason of my request was to figure out why any of the standard
linux functions
(e.g. pause, sleep,..., whether called from the linux or RT task)
results in a system lock up and why the functions rt_task_wait and
rt_task_sleep, for example, produce the error behaviour described in the
first mail.
So I think of an timer issue, or a wrong xenomai configuration or
something like this, but can't really
figure out the problem...
> Just for comparison:
> I'm running Xenomai 2.1 with Kernel 2.6.15.7 on Debian 3.1.
>
Iam running Xenomai version 2.2 and Kernel 2.6.15 on a kanotix system.
>
> Regards,
> Bernhard
>
>
>
>
Thanks for your help and time.
Regards,
Steve
next prev parent reply other threads:[~2006-08-26 21:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 14:42 [Xenomai-help] Problems with rt_task_wait_period Steve Kreyer
2006-08-07 15:27 ` Jan Kiszka
2006-08-07 15:32 ` Philippe Gerum
2006-08-25 15:31 ` [Xenomai-help] Timer problems? Steve Kreyer
2006-08-25 17:47 ` Jan Kiszka
2006-08-26 20:34 ` Steve Kreyer
2006-08-27 10:38 ` Jan Kiszka
2006-08-27 12:08 ` Philippe Gerum
2006-08-27 12:24 ` Bernhard Walle
2006-08-28 14:46 ` Philippe Gerum
2006-08-27 12:34 ` Gilles Chanteperdrix
2006-08-27 13:02 ` Philippe Gerum
2006-08-27 13:56 ` Jan Kiszka
2006-08-27 13:47 ` Steve Kreyer
2006-08-27 14:22 ` Philippe Gerum
2006-08-27 14:25 ` Philippe Gerum
2006-08-27 14:45 ` Steve Kreyer
[not found] ` <44F196A0.2030006@domain.hid>
2006-08-27 13:00 ` Steve Kreyer
2006-08-25 17:57 ` [Xenomai-help] " Bernhard Walle
2006-08-26 21:23 ` Steve Kreyer [this message]
2006-08-26 21:38 ` Bernhard Walle
2006-08-26 22:12 ` Philippe Gerum
2006-08-27 9:21 ` Steve Kreyer
2006-08-27 9:34 ` Philippe Gerum
2006-08-27 10:31 ` Gilles Chanteperdrix
2006-08-27 9:27 ` Steve Kreyer
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=44F0BBB7.7030703@domain.hid \
--to=steve.kreyer@domain.hid \
--cc=Bernhard.Walle@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.