Your stack trace shows that this is due to the latest patch to back-bdb/cache.c, rev 1.175. If you revert that patch this deadlock will go away. But that's probably not the ultimate solution.
Aaron Richton wrote:
Current function is ldap_pvt_thread_mutex_lock 296 return ERRVAL( pthread_mutex_lock( mutex ) ); t@12 (l@12) stopped in __lwp_park at 0xff1654b0 0xff1654b0: __lwp_park+0x0010: ta %icc,0x00000008 (dbx) print *mutex *mutex = { __pthread_mutex_flags = { __pthread_mutex_flag1 = 4U __pthread_mutex_flag2 = '\0' __pthread_mutex_ceiling = '\0' __pthread_mutex_type = 0 __pthread_mutex_magic = 19800U } __pthread_mutex_lock = { __pthread_mutex_lock64 = { __pthread_mutex_pad = "" } __pthread_mutex_lock32 = { __pthread_ownerpid = 0 __pthread_lockword = 4278190081U } __pthread_mutex_owner64 = 4278190081ULL }