From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 30 15:00:41 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58C8C16A40F for ; Fri, 30 Jun 2006 15:00:41 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22943443E6 for ; Fri, 30 Jun 2006 15:00:41 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5UF0eTF066519 for ; Fri, 30 Jun 2006 15:00:40 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5UF0ePp066518; Fri, 30 Jun 2006 15:00:40 GMT (envelope-from gnats) Date: Fri, 30 Jun 2006 15:00:40 GMT Message-Id: <200606301500.k5UF0ePp066518@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?ISO-8859-1?Q?Eirik_=D8verby?= Cc: Subject: Re: kern/99094: panic: sleeping thread (Sleeping thread ... owns a non-sleepable lock) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Eirik_=D8verby?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jun 2006 15:00:41 -0000 The following reply was made to PR kern/99094; it has been noted by GNATS. From: =?ISO-8859-1?Q?Eirik_=D8verby?= To: John Baldwin Cc: bug-followup@freebsd.org Subject: Re: kern/99094: panic: sleeping thread (Sleeping thread ... owns a non-sleepable lock) Date: Fri, 30 Jun 2006 16:56:14 +0200 Hm, I thought I had that in my report? I have to find a way to automate this. I've just moved the installation to a newly partitioned array, to make sure I have room for crash dumps, and I have the following in rc.conf: dumpdev="AUTO" dumpdir="/usr/crash" from my reading, that should be enough. In addition I added KDB_UNATTENDED to the kernel config, as I cannot risk that the box is down for hours before I have a chance to get to the debugger console every time. The question is: Will it actually do an automatic dump before rebooting, or will a dump *always* require manual intervention? And will a dump contain all necessary information? Thanks, /Eirik On Jun 29, 2006, at 1:26 PM, John Baldwin wrote: > You need to get a stack trace of the thread mentioned in the message > that actually misbehaved. It actually should have been printed on > the console when it panic'd since you have DDB in the kernel. > > -- > John Baldwin > >