From owner-freebsd-security Tue Mar 27 23:32:54 2001 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id BC12837B71A for ; Tue, 27 Mar 2001 23:32:43 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2S7VI390263; Wed, 28 Mar 2001 09:31:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matt Piechota Cc: mike , security@FreeBSD.ORG Subject: Re: named dying on INSIST In-Reply-To: Your message of "Tue, 27 Mar 2001 17:27:13 CDT." Date: Wed, 28 Mar 2001 09:31:18 +0200 Message-ID: <90261.985764678@critter> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Mat t Piechota writes: >> >> Mar 24 02:04:53 ns1 named[6470]: >> /usr/src/lib/libbind/../../contrib/bind/lib/isc/ev_timers.c:114: >> INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) failed. >> Mar 24 02:04:54 ns1 /kernel: pid 6470 (named), uid 53: exited on signal >> 6 > >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. I will have to add a sub-mode to the timecounters to use a fucked up TSC to interpolate between interrrupts from a better time source. I have no idea when I will have time for that... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message