From owner-freebsd-current  Wed Nov  6 15:20:26 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4A6A937B413
	for <current@FreeBSD.ORG>; Wed,  6 Nov 2002 15:20:25 -0800 (PST)
Received: from InterJet.elischer.org (12-232-206-8.client.attbi.com [12.232.206.8])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D493543E3B
	for <current@FreeBSD.ORG>; Wed,  6 Nov 2002 15:20:24 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA01545;
	Wed, 6 Nov 2002 15:01:20 -0800 (PST)
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?
In-Reply-To: <74927039.1036593999@[192.168.1.20]>
Message-ID: <Pine.BSF.4.21.0211061458220.726-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

<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