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. -- btw the upgrade to the ipipe patch in master made all xeno-regression-test problems go away - thanks! -Michael _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
