Date: Thu, 29 Mar 2001 13:48:07 -0500 (EST) From: Matt Piechota <piechota@argolis.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: mike <mike@coloradosurf.com>, <security@FreeBSD.ORG> Subject: Re: named dying on INSIST Message-ID: <Pine.BSF.4.31.0103291343560.7951-100000@cithaeron.argolis.org> In-Reply-To: <90261.985764678@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.31.0103291343560.7951-100000>