From owner-freebsd-security Thu Mar 29 10:48:44 2001 Delivered-To: freebsd-security@freebsd.org Received: from cithaeron.argolis.org (bgm-24-94-35-22.stny.rr.com [24.94.35.22]) by hub.freebsd.org (Postfix) with ESMTP id 6808137B71E for ; Thu, 29 Mar 2001 10:48:36 -0800 (PST) (envelope-from piechota@argolis.org) Received: from localhost (piechota@localhost) by cithaeron.argolis.org (8.11.3/8.11.3) with ESMTP id f2TIm7011605; Thu, 29 Mar 2001 13:48:08 -0500 (EST) (envelope-from piechota@argolis.org) X-Authentication-Warning: cithaeron.argolis.org: piechota owned process doing -bs Date: Thu, 29 Mar 2001 13:48:07 -0500 (EST) From: Matt Piechota To: Poul-Henning Kamp Cc: mike , Subject: Re: named dying on INSIST In-Reply-To: <90261.985764678@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 28 Mar 2001, Poul-Henning Kamp wrote: > >My machine does this constantly. Are you also getting "microuptime wnet > >backwards" messages on the consle/syslog? > > Sigh, I thought Intel couldn't fuck up the Pentium family anymore > when it came to timekeeping, but they've done it again with the > new clock-throtteling stuff. Just to make sure: my particular machine is an AMD K6-2 350 on a VIA Apollo based motherboard. So on my machine is a problem with the board, not clock reduction stuff. Although the point is valid, it's not the case this time around. Oddly enough, I haven't had a 'microuptime went backwards' message in the last couple days, since I've cvsup'd. -- Matt Piechota Finger piechota@emailempire.com for PGP key AOL IM: cithaeron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message