Re: clock drifts after upgrade from 5.x to 6.x
Bill Moran wrote: On Wed, 22 Mar 2006 00:46:57 + John Murphy [1]<[EMAIL PROTECTED]> wrote: Alfred Morgan [2]<[EMAIL PROTECTED]> wrote: I have upgraded 4 different machines from various FreeBSD versions of 5 to various versions of 6 and 3 of the machines has a problem where the clock will drift very quickly slowing about 2 seconds per minute. Interesting. Were all the upgrades from versions less than 5.3 I wonder? Reason I ask is that many people (including me) seem to have started having problems with ntp around that time. There was a thread in the stable mailing list about it here: [3]http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 Most machines these days have a number of clocks available. ACPI is likely choosing a less accurate clock than you would like. Apparently, with ACPI disabled, the default clock is pretty accurate. The worst examples of this are when you get calcru() errors because the clock actually appears to tick backwards sometimes. You can manually tell FreeBSD which clock to use via sysctl. I don't remember the magic incanation, but a few google searches should set you on the right path. Search for timecounter and calcru in addition to other terms relevent to your issue. No the other way around: ACPI enabled = clock works fine. ACPI disabled = clock drifts too fast for ntpd (/var/db/ntp.drift file is maxed out at 500.000) ok, Thank you Bill, I found the difference: working machine shows kern.timecounter.hardware: ACPI-fast drifting machine show kern.timecounter.hardware: TSC I will now try my other clock by setting this in my /etc/sysctl.conf: kern.timecounter.hardware=i8254 -alfred References 1. mailto:[EMAIL PROTECTED] 2. mailto:[EMAIL PROTECTED] 3. http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: clock drifts after upgrade from 5.x to 6.x
On Wed, 22 Mar 2006 00:46:57 + John Murphy <[EMAIL PROTECTED]> wrote: > Alfred Morgan <[EMAIL PROTECTED]> wrote: > > > > > I have upgraded 4 different machines from various FreeBSD versions of > > 5 to various versions of 6 and 3 of the machines has a problem where > > the clock will drift very quickly slowing about 2 seconds per minute. > >Interesting. Were all the upgrades from versions less than 5.3 >I wonder? Reason I ask is that many people (including me) seem to >have started having problems with ntp around that time. There was >a thread in the stable mailing list about it here: >http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 Most machines these days have a number of clocks available. ACPI is likely choosing a less accurate clock than you would like. Apparently, with ACPI disabled, the default clock is pretty accurate. The worst examples of this are when you get calcru() errors because the clock actually appears to tick backwards sometimes. You can manually tell FreeBSD which clock to use via sysctl. I don't remember the magic incanation, but a few google searches should set you on the right path. Search for timecounter and calcru in addition to other terms relevent to your issue. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: clock drifts after upgrade from 5.x to 6.x
I have now enabled ACPI on one machine (making the computer more unstable) and it has stopped drifting. ntpd was disabled for this test. Now that it shows it stopped drifting I have enabled ntpd to see if that causes problems. On another machine I have left ACPI disabled and restarted ntpd (with -g) and exactly 6 hours later I got: Mar 21 16:44:13 ntpd[19918]: time reset +3521.285507 s Mar 21 16:44:13 ntpd[19918]: kernel time sync disabled 6041 I tried looking in timex.h to see what 6041 ment but I could not figure out if 6041 is a mode code or status code. John Murphy wrote: Interesting. Were all the upgrades from versions less than 5.3 I wonder? Reason I ask is that many people (including me) seem to have started having problems with ntp around that time. There was a thread in the stable mailing list about it here: http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 Perhaps the ntp problem is related to what you're seeing and not an ntp problem at all. Someone raised a bug report at ntp.isc.org https://ntp.isc.org/bugs/show_bug.cgi?id=452 but it has had no action. Sorry it's only a hunch and not a solution. Versions were 5.3 or 5.4 upgraded to 6.0 or 6.1 -alfred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: clock drifts after upgrade from 5.x to 6.x
Alfred Morgan <[EMAIL PROTECTED]> wrote: > > I have upgraded 4 different machines from various FreeBSD versions of > 5 to various versions of 6 and 3 of the machines has a problem where > the clock will drift very quickly slowing about 2 seconds per minute. Interesting. Were all the upgrades from versions less than 5.3 I wonder? Reason I ask is that many people (including me) seem to have started having problems with ntp around that time. There was a thread in the stable mailing list about it here: http://docs.freebsd.org/cgi/mid.cgi?20050401104508.GJ71384 Perhaps the ntp problem is related to what you're seeing and not an ntp problem at all. Someone raised a bug report at ntp.isc.org https://ntp.isc.org/bugs/show_bug.cgi?id=452 but it has had no action. Sorry it's only a hunch and not a solution. -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
clock drifts after upgrade from 5.x to 6.x
I have upgraded 4 different machines from various FreeBSD versions of 5 to various versions of 6 and 3 of the machines has a problem where the clock will drift very quickly slowing about 2 seconds per minute. These are the machines with dmesg | grep time: (specs from [1]www.hp.com) *(no drift) HP pavilion a510n (Via KM400A, ASUS A7V8X-LA) Timecounter "i8254" frequency 1193182 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 pmtimer0 on isa0 Timecounter "TSC" frequency 2100094312 Hz quality 800 Timecounters tick every 1.000 msec *(bad drift) HP pavilion a510n (Via KM400A, ASUS A7V8X-LA) Timecounter "i8254" frequency 1193182 Hz quality 0 pci0: at device 17.5 (no driver attached) pmtimer0 on isa0 Timecounter "TSC" frequency 2100088469 Hz quality 800 Timecounters tick every 1.000 msec *(bad drift) Compaq Presario SR1230NX (Via KM400A, A7V8Z-LA) *(bad drift) Compaq Presario S6500NX (Via KM400, ASUS A7V8X-LA) Timecounter "TSC" frequency 2158040786 Hz quality 800 Timecounters tick every 1.000 msec Timecounter "i8254" frequency 1193182 Hz quality 0 The one computer that did work (the first HP pavilion a510n) seems to be the only one with ACPI enabled. -alfred References 1. http://www.hp.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
