From owner-freebsd-current@FreeBSD.ORG Tue May 17 15:32:14 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 6176616A4CE for ; Tue, 17 May 2005 15:32:14 +0000 (GMT) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 507F943D9B for ; Tue, 17 May 2005 15:32:13 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DY3yv-0006c4-2w for freebsd-current@freebsd.org; Tue, 17 May 2005 17:27:41 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 May 2005 17:27:41 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 May 2005 17:27:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Tue, 17 May 2005 08:26:11 -0700 Lines: 26 Message-ID: References: <20050516194321.GB67032@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.9.0 Sender: news Subject: Re: SMP hard lock with libpthread (thread X holds Y but isn't blocked on a lock) 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: Tue, 17 May 2005 15:32:14 -0000 Kris Kennaway wrote: > On Mon, May 16, 2005 at 08:33:14AM -0700, othermark wrote: >> I have an application that uses shared memory/threads and is linked with >> libpthread, running on May 10 -current. Every time I run it, after a few >> minutes *poof* hard lock on a SMP box. All debug options are enabled in >> the kernel, but it won't break to debugger. Here's what appears on the >> console, and addr2line output follows: > > Try the NMI debugger patches, which might be sufficient to get it into > DDB. > > Kris Jonathan's report on this issue, does have the stack trace, but seems to be triggered by nfs. http://article.gmane.org/gmane.os.freebsd.current/69268 However, simply recompiling my application with libthr instead of libpthread completely avoids the panic. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);