Date: Tue, 17 May 2005 08:26:11 -0700 From: othermark <atkin901@yahoo.com> To: freebsd-current@freebsd.org Subject: Re: SMP hard lock with libpthread (thread X holds Y but isn't blocked on a lock) Message-ID: <d6d2dg$mjk$1@sea.gmane.org> References: <d6aef1$bmc$1@sea.gmane.org> <20050516194321.GB67032@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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);
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6d2dg$mjk$1>