From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 17:47:58 2004 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 9362916A4CE for ; Thu, 9 Dec 2004 17:47:58 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D18343D53 for ; Thu, 9 Dec 2004 17:47:58 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB9HjSjj058033 for ; Thu, 9 Dec 2004 12:45:28 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)iB9HjSpb058030 for ; Thu, 9 Dec 2004 12:45:28 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Thu, 9 Dec 2004 12:45:28 -0500 (EST) From: "Andrew R. Reiter" To: current@Freebsd.org Message-ID: <20041209124257.X57958@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: panic not going to debugger? 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, 09 Dec 2004 17:47:58 -0000 Anyone else experiencing issues when a panic, something simple like a recursion on a non-recursable lock, occurs, it won't break to DDB? I've got all the right bits for it (KERNCONF options etc) but seems to have stopped working since I updated to CURRENT yesterday... after battling through trying to figure out the do_powerstate=0 issue I was having. I have a easily reproducible panic but can't dump or anything b/c of this problem. So, instead, I'll have to send an email with old information (line #'s etc)... Did I miss something? :-) Cheers, Andrew -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org