From owner-freebsd-current@FreeBSD.ORG Mon Oct 25 06:32:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 770FF16A4CE for ; Mon, 25 Oct 2004 06:32:02 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF1543D45 for ; Mon, 25 Oct 2004 06:32:02 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) i9P6VwuE043059; Mon, 25 Oct 2004 02:31:58 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i9P6Vv8k043056; Mon, 25 Oct 2004 02:31:58 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Mon, 25 Oct 2004 02:31:57 -0400 (EDT) From: Andre Guibert de Bruet To: Kris Kennaway In-Reply-To: <20041025024034.GA25830@xor.obsecurity.org> Message-ID: <20041025022803.T42571@alpha.siliconlandmark.com> References: <20041025024034.GA25830@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: named and KSE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 06:32:02 -0000 On Sun, 24 Oct 2004, Kris Kennaway wrote: > This SMP 5.3-STABLE system updated yesterday acts as a resolver for a > bunch of package clients. I just got this message in the logs: > > Oct 25 01:45:00 pointyhat named[281]: *** POKED TIMER *** > > This comes from contrib/bind9/lib/isc/timer.c: > > /* > * This is a temporary (probably) hack to fix a bug on tru64 5.1 > * and 5.1a. Sometimes, pthread_cond_timedwait() doesn't actually > * return when the time expires, so here, we check to see if > * we're 15 seconds or more behind, and if we are, we signal > * the dispatcher. This isn't such a bad idea as a general purpose > * watchdog, so perhaps we should just leave it in here. > */ > > and suggests it could be a threading bug. Just another data point: I'm seeing this on my home network's name resolver. It is an SMP machine running CURRENT w/SCHED_4BSD. FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Oct 22 15:04:44 EDT 2004 root@bling.home:/usr/CURRENT/sys/i386/compile/BLING i386 Regards, | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >