Date: Tue, 05 Nov 2002 10:35:48 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@FreeBSD.ORG, "Joel M. Baldwin" <qumqats@outel.org> Subject: Re: Why is my -current system Hard Locking? Message-ID: <XFMail.20021105103548.jhb@FreeBSD.org> In-Reply-To: <15815.56296.463941.374808@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05-Nov-2002 Andrew Gallatin wrote: > > Joel M. Baldwin writes: > > <...> > > don't think this is related to the X FP problem ( although I am > > running X11 ). There have been many times when I'd walk in the > <...> > > options DDB #Enable the kernel debugger > <...> > > Its likley you are panic'ing in X, and the system is waiting at the > ddb prompt. But you can't see it or do anything, since X has control > of the graphics and kbd, so it looks like the machine is frozen. > > Try adding options DDB_UNATTENDED to your config. Or just do > sysctl debug.debugger_on_panic=0 > > Both of these have the same effect: they will prevent ddb from stopping > the panic. Make sure you have a dump device setup to capture a > crashdump. DDB is smart enough (if you are using sc(4)) to notice that the display is in graphics mode and won't drop into a debugger prompt if you panic. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.20021105103548.jhb>