Date: Tue, 2 Jul 2002 18:38:50 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@freebsd.org Subject: Re: KSE signal problems still Message-ID: <Pine.BSF.4.21.0207021834220.97650-100000@InterJet.elischer.org> In-Reply-To: <15650.19753.171293.625675@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0207021834220.97650-100000>