From owner-freebsd-current Fri Sep 8 7: 4:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by hub.freebsd.org (Postfix) with ESMTP id E4C6137B509 for ; Fri, 8 Sep 2000 07:04:49 -0700 (PDT) Received: from host62-6-66-155.btinternet.com ([62.6.66.155] helo=btinternet.com) by tungsten.btinternet.com with esmtp (Exim 3.03 #83) id 13XOlo-00005A-00 for freebsd-current@freebsd.org; Fri, 08 Sep 2000 15:04:48 +0100 Message-ID: <39B8E82C.57C4ED7@btinternet.com> Date: Fri, 08 Sep 2000 14:22:52 +0100 From: John Toon X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: microuptime() went backwards / SHMSEG References: <20000907191913.A93124@virtual-voodoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Ames wrote: > > Just upgraded to -CURRENT as of about noon (EST) today. At reboot > I got a lot of these: > > 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? > > -Steve If it is of any relevance, I got hundreds of these messages from 4.0-RELEASE, on my Athlon 1Ghz, Abit KA7-100 system. So many, in fact, that every time it happened, I was left with no choice but to reboot, as it slowly brought the system to its knees. Building the kernel without apm fixed the problem, and I have since had no problems. -- "I'm entirely unaccountable for any moments of sanity contained herein." :s/Windows/UNIX John Toon | j.a.toon@btinternet.com | "Sonnilon" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message