-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Salutations --
I have an old board with an installation of STABLE whose time keeps
running away. ntpd is not helping. I can manually set the time using
ntpdate, and my ntpq queries look fine, yet the clock persists in
running very fast (seems to be about 1.5x speed). The BIOS clock
remains correct, and the machine therefore has the correct time at each
reboot, but quickly runs away.
Data points:
- - I have set kern.timecounter.hardware=TSC, and this has not helped.
- - Two other hosts on the same network, using the same ntp server, do not
have this problem.
- - This box did not display this behavior under FreeBSD 5.2.
- - I have replaced the board on the problem box (with the same age
and type), and the problem persists.
- - dmesg for this machine, an old Dell Optiplex 590,
is below.
What other information might help diagnose the problem?
Thank you ... -d
- --
David Talkington
dtalk-ml@prairienet.org
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.3-STABLE #0: Sat Dec 25 18:55:20 PST 2004
root@atlantis.flyingjoke.org:/usr/obj/usr/src/sys/CERBERUS
WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant
WARNING: MPSAFE network stack disabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Pentium/P54C (85.52-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x525 Stepping = 5
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 67108864 (64 MB)
avail memory = 56074240 (53 MB)
Intel Pentium detected, installing workaround for F00F bug
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
isab0: <PCI-ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
pci0: <old, VGA-compatible display device> at device 11.0 (no driver
attached)
atapci0: <GENERIC ATA controller> irq 14 at device 12.0 on pci0
ata2: channel #0 on atapci0
device_attach: ata2 attach returned 6
cpu0 on motherboard
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
pmtimer0 on isa0
ep0: <3Com 3C509-TP EtherLink III> at port 0x220-0x22f irq 11 on isa0
ep0: Ethernet address: 00:20:af:06:9e:35
ep0: [GIANT-LOCKED]
ep1: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0
ep1: Ethernet address: 00:20:af:08:7a:c2
ep1: [GIANT-LOCKED]
ep2: <3Com 3C509-TP EtherLink III> at port 0x210-0x21f irq 5 on isa0
ep2: Ethernet address: 00:20:af:ec:c4:c6
ep2: [GIANT-LOCKED]
ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0
ata1 at port 0x376,0x170-0x177 irq 15 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA (mono) <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3b0-0x3cf iomem 0xa0000-0xbffff on isa0
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
ppc1: parallel port not found.
unknown: <PNP0700> can't assign resources (port)
Timecounter "TSC" frequency 85517886 Hz quality 800
Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled
ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to
deny, logging unlimited
ad0: 515MB <WDC AC2540F/27.25C38> [1048/16/63] at ata0-master PIO3
Mounting root from ufs:/dev/ad0s1a
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFB03Jp5FKhdwBLj4sRAhvDAKCIs0YHcnzxN8AkS90Wr+dp7Euu7wCgnQEP
kHY+K7GXuxL+w/cIY9hFGbc=YaTo
-----END PGP SIGNATURE-----
what do you have in :
/etc/ntp.conf
*alk-ml at prairienet.org* dtalk-ml at prairienet.org
<mailto:freebsd-stable%40freebsd.org?Subject=clock%20running%20fast&In-Reply-To=>
/Wed Dec 29 19:13:42 PST 2004/
* Previous message: Multiple Vinum Problems Since Upgrade From 4.9
To 4.10
<http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/010694.html>
* Next message: Problem mounting root from CD9660 on 4.x
<http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/010705.html>
* *Messages sorted by:* [ date ]
<http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/date.html#10697>
[ thread ]
<http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/thread.html#10697>
[ subject ]
<http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/subject.html#10697>
[ author ]
<http://lists.freebsd.org/pipermail/freebsd-stable/2004-December/author.html#10697>
------------------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Salutations --
I have an old board with an installation of STABLE whose time keeps
running away. ntpd is not helping. I can manually set the time using
ntpdate, and my ntpq queries look fine, yet the clock persists in
running very fast (seems to be about 1.5x speed). The BIOS clock
remains correct, and the machine therefore has the correct time at each
reboot, but quickly runs away.
Data points:
- - I have set kern.timecounter.hardware=TSC, and this has not helped.
- - Two other hosts on the same network, using the same ntp server, do not
have this problem.
- - This box did not display this behavior under FreeBSD 5.2.
- - I have replaced the board on the problem box (with the same age
and type), and the problem persists.
- - dmesg for this machine, an old Dell Optiplex 590,
is below.
What other information might help diagnose the problem?
Thank you ... -d
- --
David Talkington
dtalk-ml at prairienet.org
<http://lists.freebsd.org/mailman/listinfo/freebsd-stable>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Federico Galvez-Durand Besnard wrote:> what do you have in : > /etc/ntp.confOnly: server time.u.washington.edu server 127.127.1.0 fudge 127.127.1.0 stratum 10 Command line: /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ - -f /var/db/ntpd.drift Thank you ... -d> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Salutations -- > > I have an old board with an installation of STABLE whose time keeps running > away. ntpd is not helping. I can manually set the time using ntpdate, and my > ntpq queries look fine, yet the clock persists in running very fast (seems to > be about 1.5x speed). The BIOS clock remains correct, and the machine > therefore has the correct time at each reboot, but quickly runs away. > > Data points: > > - - I have set kern.timecounter.hardware=TSC, and this has not helped. - - Two > other hosts on the same network, using the same ntp server, do not have this > problem. > - - This box did not display this behavior under FreeBSD 5.2. - - I have > replaced the board on the problem box (with the same age and type), and the > problem persists. > - - dmesg for this machine, an old Dell Optiplex 590, is below. > > What other information might help diagnose the problem? > > Thank you ... -d > > - -- > David Talkington > dtalk-ml at prairienet.org > <http://lists.freebsd.org/mailman/listinfo/freebsd-stable> > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >- -- David Talkington Computing and Communications University of Washington 206-543-2144 - -- dtalk@u.washington.edu - -- PGP key: http://staff.washington.edu/dtalk/004B8F8B.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB1FN55FKhdwBLj4sRAknTAJ9Wq/I64DpzBoblMmH2JMl2UR08NgCgkLuL qlB7DOSkWlOmR2OLZ32O1NA=8B5z -----END PGP SIGNATURE-----
Set /etc/localtime to your correct timezone before doing anything in your machine. Remove /var/db/ntpd.drift before you reboot or restart your ntpd. This is what I use in /etc/rc.conf: +++ ntpd_enable="YES" # Run ntpd Network Time Protocol (or NO). ntpd_program="/usr/sbin/ntpd" # path to ntpd, if you want a different one. ntpd_flags="-p /var/run/ntpd.pid -f /etc/ntp/drift -l /var/log/ntp.log" +++ Check ntpd messages with dmesg. If it does not work, this is one ntp.conf (change server to time.u.washington.edu or whatever is closer to you) that worked well for me: +++++ BEGIN /etc/ntp.conf +++++++ # NTP configuration file # # Thu Nov 11 20:06:40 GMT+1 2004 restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap restrict 127.0.0.1 # servers to query #------------------- server clock.tix.ch restrict clock.tix.ch mask 255.255.255.255 nomodify notrap noquery +++++ END /etc/ntp.conf +++++++ Once you get synchronised with your time-server, you can consider changing minpoll maxpoll to polite values. Fico// David Talkington wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Federico Galvez-Durand Besnard wrote: > >> what do you have in : >> /etc/ntp.conf > > > Only: > > server time.u.washington.edu > server 127.127.1.0 fudge 127.127.1.0 stratum 10 > > > Command line: > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid \ > - -f /var/db/ntpd.drift > > Thank you ... -d >
> [ rc.conf and ntp.conf snipped ] > > Thank you for the suggestions. Unfortunately, I've been through all > that, including the rude values of minpoll and maxpoll, using multiple > servers, and starting with a fresh drift file. I'm pretty sure ntpd > isn't the problem. In addition, the hardware clock itself appears to be > plenty accurate, as it is always correct within a second or two when I > check it directly in BIOS ... and two other 5.3-STABLE hosts on the same > network, with the same ntpd configuration, but on different hardware, do > not have this problem, which began when I updated (reinstalled) to > 5.3-STABLE from 5.2. > > - -- > David Talkington > dtalk-ml@prairienet.orgI apparently misposted this earlier, my apologies. Have you tried all possible values for kern.timecounter.hardware? #sysctl kern.timecounter.choice My most recent encounter with this issue, a K6-2/500 on an Asus P5A mobo, needed "i8254". HTH, Kevin Kinsey
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kevin Kinsey wrote:> Have you tried all possible values for kern.timecounter.hardware? > > #sysctl kern.timecounter.choice > > My most recent encounter with this issue, a K6-2/500 on an > Asus P5A mobo, needed "i8254".Thank you vociferously. A value of i8254 for kern.timecounter.hardware seems to have had the desired effect. Cheers ... -d - -- David Talkington dtalk-ml@prairienet.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB1O/d5FKhdwBLj4sRAkAcAKCkG4sD4+8sWszGSsocj0gpIAwYrQCfVNwV 24g6apBqGznNfM28YjaWZMI=P4Pa -----END PGP SIGNATURE-----