Date: Wed, 15 Dec 1999 17:09:15 +0200 (SAST) From: Khetan Gajjar <khetan@chain.freebsd.os.org.za> To: current@freebsd.org Subject: microuptime problem/error ? Message-ID: <Pine.BSF.4.10.9912151704400.77137-100000@chain.freebsd.os.org.za>
next in thread | raw e-mail | index | archive | help
Hi. I've started seeing "microuptime() went backwards" errors, followed by calcru errors. I think it's related to phk's commit of kern_resource.c (1.53) and kern_synch.c (1.84). What I don't understand is how is this possible if I'm using xntpd to keep time, and my machine is reporting itself as a stratum 3 server ? I have included three examples of the microuptime and calcru error, and the output of ntptrace. I'm running a -current with source from Dec 5th. Dec 15 16:07:53 chain /kernel: microuptime() went backwards (101123.4765911 -> 101123,992013) Dec 15 16:07:53 chain /kernel: microuptime() went backwards (101123.4765911 -> 101123,992013) Dec 15 16:07:53 chain /kernel: microuptime() went backwards (101123.4765911 -> 101123,993154) Dec 15 17:00:01 chain /kernel: calcru: negative time of 653353 usec for pid 126 (syslogd) Dec 15 17:00:01 chain /kernel: calcru: negative time of 653353 usec for pid 126 (syslogd) Dec 15 17:00:01 chain /kernel: calcru: negative time of 653353 usec for pid 126 (syslogd) localhost.freebsd.os.org.za: stratum 3, offset 0.000043, synch distance 0.17436 lo0.cr1.cpt.iafrica.net: stratum 2, offset 0.002962, synch distance 0.06694 Time1.wasp.co.za: stratum 1, offset -0.005048, synch distance 0.00087, refid 'GPS' TIA. --- Khetan Gajjar (!kg1779) * khetan@os.org.za http://khetan.os.org.za/ * Talk/Finger khetan@khetan.os.org.za FreeBSD enthusiast * http://www2.za.freebsd.org/ /dev/random output : A naked man fears no pickpocket To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912151704400.77137-100000>