On Wed, 2 Apr 2003, Gordon Tetlow wrote: > I think it was a libthr linked app after I killed it:
Yeah, this is a problem with the thread single exit and suspend code. I haven't fixed it yet. Thanks for the report. > lock order reversal > 1st 0xc679d248 process lock (process lock) @ /local/usr.src/sys/kern/kern_exit. > c:134 > 2nd 0xc05394a0 Giant (Giant) @ /local/usr.src/sys/kern/kern_exit.c:142 > Stack backtrace: > backtrace(c04e759f,c05394a0,c04e3f7f,c04e3f7f,c04e2359) at backtrace+0x17 > witness_lock(c05394a0,8,c04e2359,8e,0) at witness_lock+0x692 > _mtx_lock_flags(c05394a0,0,c04e2359,8e,c6d9deac) at _mtx_lock_flags+0xb2 > exit1(c6d9de40,f00,c04e2359,63,e9971d40) at exit1+0x174 > sys_exit(c6d9de40,e9971d14,c04ff422,404,1) at sys_exit+0x41 > syscall(2f,2f,2f,0,ffffffff) at syscall+0x24e > Xint0x80_syscall() at Xint0x80_syscall+0x1d > --- syscall (1), eip = 0x280ef90f, esp = 0xbf91071c, ebp = 0xbf910738 --- > > -gordon > _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
