From: Philippe Gerum <rpm@xenomai.org>
To: Steve Kreyer <steve.kreyer@domain.hid>
Cc: Bernhard Walle <bernhard@domain.hid>,
xenomai@xenomai.org, Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] Re: Timer problems?
Date: Sun, 27 Aug 2006 11:34:44 +0200 [thread overview]
Message-ID: <1156671284.4325.4.camel@domain.hid> (raw)
In-Reply-To: <44F16426.5010207@domain.hid>
On Sun, 2006-08-27 at 11:21 +0200, Steve Kreyer wrote:
> Hi Philippe,
>
> disabling PM in Kernel was a good tip!
>
> Now I can call standard linux library functions without resulting in a
> system lock up :)
> But the ETIMEDOUT error when calling e.g. rt_task_wait_period or
> rt_task_sleep still persists.
> The latency test gives me the following output:
>
> -------------------------------------------------------------------------------------------------------------------
> == Test mode: periodic user-mode task
> == All results in microseconds
> latency: failed to set periodic, code -110
> warming up...
> ---|------------|------------|------------|--------|-------------------------
> RTS| -208983.489| 0.000| 208983.489| 0| 00:00:26/00:00:26
> -------------------------------------------------------------------------------------------------------------------
>
> Also the attached application produces the below output:
> -------------------------------------------------------------------------------------------------------------------
> working!
> working!
> Warning: Cannot wait for task period! errcode=-110 110 timeout=1
> working!
> Warning: Cannot wait for task period! errcode=-110 110 timeout=1
> -------------------------------------------------------------------------------------------------------------------
>
> The output string "working!" and the warning messages printed at once
> and not as expected every second (see attachment)...
> The TROUBLESHOOTING file has no answer to this behaviour...
>
> Do you have any hints on this?
>
Try disabling ACPI completely, just to see if it is somehow involved.
--
Philippe.
next prev parent reply other threads:[~2006-08-27 9:34 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
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 [this message]
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=1156671284.4325.4.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=bernhard@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=steve.kreyer@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.