From owner-freebsd-current Sun Sep 30 21:43:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id DA26037B40F; Sun, 30 Sep 2001 21:43:31 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f914hVH96086; Sun, 30 Sep 2001 21:43:31 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 30 Sep 2001 21:43:30 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Mike Smith Cc: current@freebsd.org Subject: Re: reappearance of an old bug again? (microtime went backwards) In-Reply-To: <200110010450.f914oOn05597@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cool. Yes. Will do. It also turns out that even with this being an SMP system with IOAPIC that ACPI still shares an irq with isp0. How odd. On Sun, 30 Sep 2001, Mike Smith wrote: > > > > -current as of the last day or so- anyone else seen? > > > > Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041 > > microuptime() went backwards (939.4410978 -> 938.949317) > > Try turning off the ACPI timer: > > debug.acpi.disable="timer" > > in loader.conf and see if it goes away. I'm still looking for better > testing techniques, since it looks like the ACPI timer can't be trusted. 8( > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message