Date: Wed, 6 Nov 2002 15:01:19 -0800 (PST) From: Julian Elischer <julian@elischer.org> To: "Joel M. Baldwin" <qumqats@outel.org> Cc: current@FreeBSD.ORG Subject: Re: Why is my -current system Hard Locking? Message-ID: <Pine.BSF.4.21.0211061458220.726-100000@InterJet.elischer.org> In-Reply-To: <74927039.1036593999@[192.168.1.20]>
next in thread | previous in thread | raw e-mail | index | archive | help
<CTL><ALT><ESC> on the keyboard still will make the console go to the debugger, even when console is on another device (e.g. serial port) if that doesn't help, then I have no idea.. On Wed, 6 Nov 2002, Joel M. Baldwin wrote: > > No change, the system is still Hard Locking. It did it > 4 times yesterday. The next steps for me are: > > 1.) Get a serial console working. Maybe I'll get some > indication of what's happening that way. > 2.) When the serial console is working, see if I can > break into ddb after a Hard Lock. > > Is there a way in HARDWARE to FORCE a break into ddb? > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Maybe I can tell if the system is running, where it is > running, and how it got there. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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.21.0211061458220.726-100000>