try this: in tdsignal, (kern_sig.c) take a lock on schedlock and release it again, just around the call to forward-signal()
forward_signal(c4445540) at forward_signal+0x1a tdsignal(c4445540,2,2) at tdsignal+0x182 psignal(c443d558,2) at psignal+0x3c8 hopefully this will not be called with the schedlock already locked if we panic becasue we already own it, it gets more difficult.. On Tue, 2 Jul 2002, Andrew Gallatin wrote: > > Julian Elischer writes: > > > > > > On Tue, 2 Jul 2002, Andrew Gallatin wrote: > > > > > > > > Julian Elischer writes: > > > > > > > > > > > > On Tue, 2 Jul 2002, Andrew Gallatin wrote: > > > > > > > > > > > > > > An easy way to induce a panic w/a post KSE -current is to ^C gdb as it > > > > > starts on an SMP machine: > > > > > > > > A possibly related breakage is: > > > > > > > > type ^Z while doing "make buiildworld" (or something similar). > > > > > > > > when you type 'fg' there is a high change the build will abort.. > > > > > > > > > > This is nearly 100% for me. But only on MP boxes. On my uniprocessor > > > alpha, things work just fine. Oh.. hmm.. I'm not sure if I have > > > witless compiled in there.. > > > > which is almost 100%,? the ^Z killing the process, or ^C killing the > > machine? > > ^C killing the machine. > > Drew > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
