From owner-freebsd-current@FreeBSD.ORG Sat Nov 15 06:40:38 2003 Return-Path: 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 2A0FF16A4CE; Sat, 15 Nov 2003 06:40:38 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27B2E43FE0; Sat, 15 Nov 2003 06:40:37 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAFEccMg034503; Sat, 15 Nov 2003 09:38:38 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hAFEcbmI034500; Sat, 15 Nov 2003 09:38:38 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 15 Nov 2003 09:38:37 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Andy Farkas In-Reply-To: <20031115160208.D13393@hewey.af.speednet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@FreeBSD.ORG cc: jhb@FreeBSD.ORG Subject: Re: checking stopevent 2! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2003 14:40:38 -0000 On Sat, 15 Nov 2003, Andy Farkas wrote: > These messages spew onto my console and into syslogd once every second: Heh. Sounds like your box is having a really bad day, we'll see if we can't get it fixed up over the next couple of weeks as things settle out :-). I think John has this one in his sights already, we talked about the sigacts locking during the release engineering telecon yesterday (CC'd gratuitously in this message). Basically, every place where a debugger can "stop" a process there's a call to STOPEVENT(), which may sleep indefinitely waiting to be restarted by the process performing the debugging. The problem appears to be that recent changes pushed a STOPEVENT() call inside code holding a mutex, so the locking of that piece of code needs to be changed slightly to make sure that doesn't happen. IT would probably be useful if you could drop to DDB and generate a trace for the event. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories > > ... > Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:44 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 > Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:44 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > Nov 15 16:05:44 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/kern_synch.c:293 > Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:45 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 > Nov 15 16:05:45 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > Nov 15 16:05:46 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289 > Nov 15 16:05:46 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > Nov 15 16:05:46 hummer kernel: checking stopevent 2 with the following non-sleepable locks held: > Nov 15 16:05:46 hummer kernel: exclusive sleep mutex sigacts r = 0 (0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260 > ... > > > > This is latest -current (cvsup'd a few hours ago) > > > -- > > :{ andyf@speednet.com.au > > Andy Farkas > System Administrator > Speednet Communications > http://www.speednet.com.au/ > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >