Date: Wed, 18 May 2005 15:14:58 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Kris Kennaway <kris@obsecurity.org> Cc: othermark <atkin901@yahoo.com> Subject: Re: SMP hard lock with libpthread (thread X holds Y but isn'tblocked on a lock) Message-ID: <20050518151427.E87264@carver.gumbysoft.com> In-Reply-To: <20050517224142.GA12953@xor.obsecurity.org> References: <d6aef1$bmc$1@sea.gmane.org> <20050516194321.GB67032@xor.obsecurity.org> <20050517224142.GA12953@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 May 2005, Kris Kennaway wrote: > On Tue, May 17, 2005 at 08:26:11AM -0700, othermark wrote: > > 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 > > The 'turnstile' panic may be secondary, and the real panic was in some > other thread. That's why you'd need to get into DDB. Someone else posted a full trace; it looks like a locking problem in nfs_sigmask(). > > However, simply recompiling my application with libthr instead of libpthread > > completely avoids the panic. > > Obviously not a real solution.. > > Kris > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050518151427.E87264>