From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 01:18:47 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 CB76A37B401 for ; Thu, 17 Apr 2003 01:18:47 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 23C7D43FB1 for ; Thu, 17 Apr 2003 01:18:47 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 46733 invoked by uid 1000); 17 Apr 2003 08:18:49 -0000 Date: Thu, 17 Apr 2003 01:18:49 -0700 (PDT) From: Nate Lawson To: Andrew Gallatin In-Reply-To: <16029.64451.191705.186274@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Ruslan Ermilov cc: current@FreeBSD.org Subject: Re: Your locking and rman changes to pci/if_* 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: Thu, 17 Apr 2003 08:18:48 -0000 On Wed, 16 Apr 2003, Andrew Gallatin wrote: > Ruslan Ermilov writes: > > : dc0: detached > > : panic: blockable sleep lock (sleep mutex) Giant @ vm/vm_fault.c:206 > > > > Reverting to if_dc.c,v 1.96 makes the problem go away. > > Please fix. > > I think this indciates that something trap'ed in the kernel in the > middle of handling, say, another trap. > > A stack trace from ddb or gdb would make this a lot easier to debug. Yes, backtrace please. Also, you might want to try removing the bus_child_present() check in xl_detach and just unconditionally call xl_stop(). Ian Dowse has indicated to me that some of the drivers (dc) have routines which need to always be called in detach, even if the hardware is not present. -Nate