From owner-freebsd-current@FreeBSD.ORG Tue Feb 15 14:41:26 2005 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 F0C3616A4CE for ; Tue, 15 Feb 2005 14:41:26 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9783743D1F for ; Tue, 15 Feb 2005 14:41:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) j1FEfPpo015445; Tue, 15 Feb 2005 09:41:25 -0500 (EST) Date: Tue, 15 Feb 2005 09:41:25 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Ted Lindgreen In-Reply-To: <200502150905.j1F95axw000902@sanne.nlnetlabs.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: freebsd-current@freebsd.org Subject: Re: few programs now getting sig 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 14:41:27 -0000 On Tue, 15 Feb 2005, Ted Lindgreen wrote: > In article <67b8fa69de95da88c7f15fea92a26394@mcneil.com>, > Sean McNeil wrote: > ... > >#0 0x00000008009abcfc in kse_thr_interrupt () at kse_thr_interrupt.S:2 > >#1 0x000000080099c4fd in _thr_sig_add (pthread=0x50d800, sig=6, > >info=0x0) > > at /usr/src/lib/libpthread/thread/thr_sig.c:974 > >#2 0x000000080099c971 in _thr_sig_send (pthread=0x50d800, sig=6) > > at /usr/src/lib/libpthread/thread/thr_sig.c:1106 > ... > > Looks like the same problem happens also spamass-milter. > At startup spamass-milter produces some additional info > which may be helpful: > > sanne# /usr/local/etc/rc.d/spamass-milter.sh start > Starting spamass_milter. > Fatal error 'Thread has returned from _thread_switch' at line 1101 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 0) > > and a coredump analysis looks similar to above. > > This error did not occur with a kernel+world build on Febr. 12, > it consistently happens with nightly builds on Febr. 14 and 15 > (this morning). You can try backing out the increase stacksize change I committed yesterday to libpthread... I didn't have any problem testing it here. -- DE