Did you do an in-place update or a nuke-and-repave update? if it's an in-place update, then do a nuke-and-repave on your test system and see if the problem still happens. If not then there's a library or something somewhere that the updater forgot about.
Ted > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Michal Mertl > Sent: Wednesday, May 11, 2005 3:37 PM > To: [email protected] > Subject: NTP issues with 5.4 > > > Hello, > > I run ntpd in daemon mode on several FreeBSD computers and synchronize > with 'ntpd -q' all others. > > I've just updated one machine to 5.4 (from 5.3) and noticed the daemon > was unhappy, often logging 'time reset' and resynchronizing with peers. > On other machines I also only recently (after the upgrade to 5.4) see > ntp problems - 'ntpd -q' gets stuck and time goes off. The > machines were > all fine before. > > I searched the web and archives and found some more people complaining > about similar issues but I haven't found any good answer. At first I > thought it was happening only on SMP computers but it isn't the case. > The machines have all kinds of timecounters - ACPI-fast, ACPI-safe and > i8254. > > Do you have any idea? > > Michal Mertl > > _______________________________________________ > [email protected] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
