From owner-freebsd-current Sun Sep 10 5:40: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 75EC337B43C for ; Sun, 10 Sep 2000 05:40:00 -0700 (PDT) Received: from netch@localhost by burka.carrier.kiev.ua id PPJ85223; Sun, 10 Sep 2000 15:39:57 +0300 (EEST) (envelope-from netch) Date: Sun, 10 Sep 2000 15:39:57 +0300 (EEST) Message-Id: <200009101239.PPJ85223@burka.carrier.kiev.ua> From: netch@carrier.kiev.ua (Valentin Nechayev) To: John Baldwin , freebsd-current@freebsd.org Subject: Re: microuptime() went backwards In-Reply-To: <200009080028.RAA26021@pike.osd.bsdi.com> Organization: Lucky Netch Incorporated User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.5-STABLE (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello John Baldwin! >> microuptime() went backwards (1.7682417 -> 1.997434) >> >> I recall reading in -current earlier this week that someone was >> looking for victims getting this. What further information can I provide? JB> This is a SMPng issue on UP machines. I have obtained the same on non-SMP machine. (See my parallel letter.) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message