Date: Thu, 23 Aug 2001 20:27:41 -0700 From: mki <mki@mozone.net> To: freebsd-stable@FreeBSD.org Subject: microuptime() went backwards in 4.4-RC (20010816 snapshot) Message-ID: <20010823202741.G1286@cyclonus.mozone.net>
next in thread | raw e-mail | index | archive | help
Hi, On a couple of our boxes, we see these popup randomly, sometimes way too often: microuptime() went backwards (267002.298535 -> 267002.295159) microuptime() went backwards (267002.298535 -> 267002.297651) microuptime() went backwards (267002.384424 -> 267002.369886) microuptime() went backwards (267002.427783 -> 267002.402039) microuptime() went backwards (267002.577015 -> 267002.541318) microuptime() went backwards (267002.642923 -> 267002.618465) microuptime() went backwards (267002.642923 -> 267002.607871) microuptime() went backwards (267002.704413 -> 267002.667297) microuptime() went backwards (267002.907497 -> 267002.898190) microuptime() went backwards (267003.066847 -> 267003.065262) calcru: negative time of -161058988 usec for pid 1593 (perl) however, when this happens, other than syslogd chewing up the available cpu cycles, all the applications start doing wierd things because the time shifts to really odd values. We have to then reset the date and/or reboot to fix it. We've tried turning off apm in the kernel, as well as set kern.timecounter.method=1, but the problems have persisted. Any help would be greatly appreciated. -mohan 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?20010823202741.G1286>