From owner-freebsd-bugs Fri Jan 17 11:53:37 2003 Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D5EF37B401 for ; Fri, 17 Jan 2003 11:53:36 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F4043ED8 for ; Fri, 17 Jan 2003 11:53:35 -0800 (PST) (envelope-from bzeeb-lists@zabbadoz.net) Received: from localhost (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id D2E691FFF89 for ; Fri, 17 Jan 2003 20:53:28 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 17BAC1FFF4F; Fri, 17 Jan 2003 20:53:28 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 68F031537A; Fri, 17 Jan 2003 20:32:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 5F7EF15379 for ; Fri, 17 Jan 2003 20:32:11 +0000 (UTC) Date: Fri, 17 Jan 2003 20:32:11 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-bugs@FreeBSD.org Subject: 'microuptime went backwards' ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I no longer can find the "microuptime() went backwards" message in RELENG_5_0 sources I cvsuped last weekend. has this one been fixed there or is it just gone because of major changes ? May I assume that it might no longer happen ? I again read through kern/18949, i386/43491, kern/18598, kern/18858, kern/20256, kern/25788, i386/30789, kern/18798, kern/31971 because I am getting this message again. It started just the hours I started to run amanda backup server with holding disc on my machine I mentioned in i386/43491. I turned off softupdates the second night but as expected it didn't help. It at least seems it's caused by heavy disc IO. I am going to continue to play with apm and kern.timecounter but as last time I do not expect any solution. One change a night will take some days. Till then any other hints, pointers, informations mailing list threads about those timing probs, etc. would be appreciated to get this one sorted out. Thanks. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message