Date: Tue, 5 Nov 2002 11:29:08 -0600 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: "Joel M. Baldwin" <qumqats@outel.org>, current@FreeBSD.ORG Subject: Re: Why is my -current system Hard Locking? Message-ID: <20021105172908.GA36314@leviathan.inethouston.net> In-Reply-To: <15815.56296.463941.374808@grasshopper.cs.duke.edu> References: <149469335.1036439809@[192.168.1.20]> <15815.56296.463941.374808@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> <...> > > 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 > I can't seem to find the beginning of this thread, but I think I may be seeing the same problem. Whenever I try to close X I get a blank screen, but I can ssh in from another machine. I can even run startx from ssh and it brings up X on the console again. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. <www.inethouston.net> dwcjr@freebsd.org FreeBSD Committer <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?20021105172908.GA36314>