From owner-freebsd-current Tue Jul 2 18:40:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47CDA37B400 for ; Tue, 2 Jul 2002 18:40:13 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 954C343E31 for ; Tue, 2 Jul 2002 18:40:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020703014011.GYCW6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Wed, 3 Jul 2002 01:40:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA99783; Tue, 2 Jul 2002 18:38:51 -0700 (PDT) Date: Tue, 2 Jul 2002 18:38:50 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: freebsd-current@freebsd.org Subject: Re: KSE signal problems still In-Reply-To: <15650.19753.171293.625675@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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