Date: Wed, 1 Aug 2001 02:51:58 -0500 (CDT) From: David Scheidt <dscheidt@tumbolia.com> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: Vincent Poy <vince@oahu.WURLDLINK.NET>, John Baldwin <jhb@FreeBSD.org>, Kris Kennaway <kris@obsecurity.org>, <current@FreeBSD.org> Subject: Re: -current lockups Message-ID: <Pine.BSF.4.32L2.0108010249460.22458-100000@shell-1.enteract.com> In-Reply-To: <95442.996651183@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.32L2.0108010249460.22458-100000>