Port-next68k archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Flaky timekeeping?

Sounds like you've narrowed it down to a software issue. Although the hardware is known to have imperfections, as well as a large discrepancy between the battery-powered RTC and the running timer, it seems like at least some builds can keep a decent clock.

Now, if only you could merge the working SCSI support with the working time code!

Brian Willoughby
Sound Consulting

On Jan 7, 2014, at 00:11, Mouse wrote:
Since writing my list mail, I've tried 1.4T (I forget what pushed me to - compiler taking a very long time to run maybe?). Under 1.4T, the drift is much closer to constant. xntpd (1.4T uses xntpd, not ntpd) showed drift too, but, like ntpd on 4.0.1, it was large enough that it wouldn't sync;

Given the differences here, there is clearly some substantial software difference. Based on the drastic difference in the drift's variance, I am inclined to blame 4.0.1. For my purposes, I'm just sticking with 1.4T for now - on this hardware the only benefit 4.0.1 offers over it for me is SCSI support, which for my purposes is minor compared to half-decent timekeeping and a usable compiler - and either just living with the clock drift or, if I get annoyed enough, bashing the clock tick figure to correct for an approximation to the mean drift so NTP can take it the rest of the way.

Home | Main Index | Thread Index | Old Index