On Sat, Mar 18, 2006 at 02:28:24PM -0500, Steven S wrote:
> Joachim Schipper wrote:
> >> Using NTPDATE in cron (30 minutes), I was able to handle this weird
> >> behavior.
> >>
> >> Take a look in your date/time, maybe it's the reason of your strange
> >> carp issues.
> >
> > As to problems with adjtime(2) and SMP machines, there is a small
> > diff from tedu@ on tech@ at
> > http://marc.theaimsgroup.com/?l=openbsd-tech&m=113592306900483&w=2,
> > which stemmed from the discussion on misc@ around the same time,
> > involving another SMP machine with severely screwed timekeeping - in
> > fact, it was so bad that NTPd couldn't keep up. Ted's diff
> > allows NTP to
> > keep up with time slew even on very imprecise hosts.
> >
> > It's a workaround, but might work for you.
>
> I tried the patch, but it didn't apply cleanly against 3.8:-(
>
> I tried booting FW2 with the SP kernel, but the problem still persists. It
> doesn't appear to be ntpd related since ntp updates didn't correlate with
> carp BACKUP -> MASTER transitions. I'll keep plugging away at it...
Nonetheless, it does lead to the question if timekeeping, especially
without ntpd, is accurate. You seem to believe this is not the case;
fixing this might well fix the carp problems.
Joachim
