From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <mail17@mah.priv.at>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [Emc-developers] "new RTOS" status: Scheduler (?) lockup on ARM
Date: Mon, 21 Jan 2013 20:10:11 +0100 [thread overview]
Message-ID: <50FD9293.4060304@xenomai.org> (raw)
In-Reply-To: <327290E8-7EDA-4ED8-80DC-93ADEB393C9F@mah.priv.at>
On 01/21/2013 02:32 PM, Michael Haberler wrote:
>
> Am 21.01.2013 um 12:56 schrieb Gilles Chanteperdrix:
>
>> On 01/21/2013 12:43 PM, Michael Haberler wrote:
>>
>>> the suspicion now turned to the DHCP lease setting and RTC time
>>> warp issues - the Beaglebone doesnt have an RTC so it starts up
>>> at 1-1-1970
>>>
>>> the first DHCP lease still has 1970 timestamps, but eventually
>>> the RTC is set with ntpdate and it could be this causes
>>> confusion
>>>
>>> the thing which is hard to believe for me: loss of IP
>>> connectivity - conceivable; kernel hang - why?
>>>
>>> question: does a RTC time warp have any possible bearing on
>>> Xenomai operations?
>>
>>
>> No, it should not, Xenomai uses its own clock, which is set only
>> once upon boot, so, is unaffected by Linux wallclock time
>> changes... or should be.
>
>
> it might not be Xenomai after all. Uhum.
>
> the bughunt safari tribe has decided to focus on class 'duh' problems
> and resolves to shut up until red hands are spotted.
I would still put the check in the timer "set_next_event" callback, just
in case...
--
Gilles.
next prev parent reply other threads:[~2013-01-21 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D4F8D1B-022E-47F8-A579-EBF2A3427C5D@mah.priv.at>
[not found] ` <50F6D940.3040406@xs4all.nl>
[not found] ` <F1ACE4FC-3E71-4498-B683-81F5C40CB6E3@mah.priv.at>
2013-01-17 7:59 ` [Xenomai] [Emc-developers] "new RTOS" status: Scheduler (?) lockup on ARM Bas Laarhoven
2013-01-17 8:53 ` Gilles Chanteperdrix
2013-01-17 11:34 ` Michael Haberler
2013-01-17 12:07 ` Gilles Chanteperdrix
2013-01-17 13:30 ` Bas Laarhoven
2013-01-19 13:29 ` Gilles Chanteperdrix
2013-01-19 14:09 ` Michael Haberler
2013-01-19 14:10 ` Gilles Chanteperdrix
2013-01-19 14:14 ` Michael Haberler
2013-01-19 14:19 ` Gilles Chanteperdrix
2013-01-19 14:32 ` Gilles Chanteperdrix
2013-01-21 11:43 ` Michael Haberler
2013-01-21 11:56 ` Gilles Chanteperdrix
2013-01-21 13:32 ` Michael Haberler
2013-01-21 19:10 ` Gilles Chanteperdrix [this message]
2013-01-21 21:20 ` Michael Haberler
2013-01-22 12:06 ` [Xenomai] [Emc-developers] "new RTOS" status: Scheduler (?) lockup on ARM - SUMMARY Bas Laarhoven
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=50FD9293.4060304@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mail17@mah.priv.at \
--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.