From owner-freebsd-stable Thu Nov 11 14:18:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 848E314E3D for ; Thu, 11 Nov 1999 14:18:57 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA02684 for ; Thu, 11 Nov 1999 17:18:55 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA04569 for ; Thu, 11 Nov 1999 17:18:54 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id RAA00383 for freebsd-stable@freebsd.org; Thu, 11 Nov 1999 17:18:52 -0500 (EST) Date: Thu, 11 Nov 1999 17:18:52 -0500 (EST) From: Thomas David Rivers Message-Id: <199911112218.RAA00383@lakes.dignus.com> To: freebsd-stable@freebsd.org Subject: -- panics 3.3-RELEASE. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I think I may know why DDB isn't working well for my other problem. When I go to the console and press: -- just to see if DDB is available - *poof* - instant double panic and reboot - with no core saved. Unfortunately - the panic rolls off the screen faster than I can read it (although there does seem to be two sets of panic info.) Unlike my other panic, this doesn't hang - it reboots. I'll submit a PR for this; but, in the meantime, I'm pretty sure other people have DDB in their 3.3-RELEASE systems... don't they? - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message