From owner-freebsd-current Wed Aug 1 0:52: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by hub.freebsd.org (Postfix) with ESMTP id D801837B409; Wed, 1 Aug 2001 00:51:58 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-1.enteract.com (shell-1.enteract.com [207.229.143.40]) by smtp-2.enteract.com (Postfix) with ESMTP id 69A8B68E6; Wed, 1 Aug 2001 02:51:58 -0500 (CDT) Date: Wed, 1 Aug 2001 02:51:58 -0500 (CDT) From: David Scheidt X-X-Sender: To: Sheldon Hearn Cc: Vincent Poy , John Baldwin , Kris Kennaway , Subject: Re: -current lockups In-Reply-To: <95442.996651183@axl.seasidesoftware.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 1 Aug 2001, Sheldon Hearn wrote: : : :On Tue, 31 Jul 2001 12:06:49 -1000, Vincent Poy wrote: : :> Yeah, that's the weird part... I thought adding a DDB_UNATTENDED :> as a option would atleast make it reboot or something... : :For the record, DDB_UNATTENDED is mostly pointless. It just sets the :default value of debug.debugger_on_panic, which you can just as well set :in /etc/sysctl.conf. Unless, of course, you're seeing a panic in the :startup process. But then do you really want an indefinite panic cycle? ::-) Well, my current startup panic only happens at cold boot. After it panics the first time, it boots fine. If DDB_UNATTENED isn't set, it hangs trying to enter DDB. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message