Date: 30 Aug 2001 06:01:27 +0200 From: "clemensF" <rabat@web.de> To: freebsd-stable@FreeBSD.ORG Subject: microuptime() went backwards Message-ID: <20010830060127.L19000@spotteswoode.yi.org>
next in thread | raw e-mail | index | archive | help
the clock skew on my k2-6 pc is indicated, usually between the third and forth decimal after the dot, and i can't get it right. the problem is worst with freebsd, i did not see it with openbsd. i tried: "sysctl -w kern.timecounter.method=1", which is the standard setting now, no success. i even fiddled with "options NTIMECOUNTER=20" entries in my kernel config, this also did not help. i had the counter from 5 up to a few thousand(!), to no avail. doesn't this look like interrupts beeing masked for too long? clemens ps: typical entries in `dmesg -a` look like: Wed Aug 29 16:12:25 CEST 2001 microuptime() went backwards (7633.019507 -> 7633.019407) pid 16331 (vile), uid 65534: exited on signal 6 (core dumped) cd9660: RockRidge Extension microuptime() went backwards (27387.137508 -> 27387.137407) microuptime() went backwards (27888.555071 -> 27888.554971) microuptime() went backwards (37977.157270 -> 37977.156967) happens from thrice up to a few dozen times, depending on load. the board is a gigabyte GA-5AA, super7 mainboard with a k6-2 550Mhz, the graphics are a "bulk" Xpert@play, agp interfaced. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010830060127.L19000>