From owner-freebsd-current@FreeBSD.ORG  Sun Jun 13 03:42:06 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 D1E4916A4CE
	for <current@freebsd.org>; Sun, 13 Jun 2004 03:42:06 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6958043D1F
	for <current@freebsd.org>; Sun, 13 Jun 2004 03:42:06 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.10/8.12.10) id i5D3fcNk074582;
	Sat, 12 Jun 2004 22:41:38 -0500 (CDT)
	(envelope-from dan)
Date: Sat, 12 Jun 2004 22:41:38 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: Doug White <dwhite@gumbysoft.com>
Message-ID: <20040613034137.GC94119@dan.emsphone.com>
References: <40CAD634.8060808@anduin.net>
	<20040612142543.H74026@carver.gumbysoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040612142543.H74026@carver.gumbysoft.com>
X-OS: FreeBSD 5.2-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: Eirik Oeverby <ltning@anduin.net>
cc: current@freebsd.org
Subject: Re: Serial console - how to reboot?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jun 2004 03:42:06 -0000

In the last episode (Jun 12), Doug White said:
> If you built the kernel with 'options BREAK_TO_DEBUGGER', then a
> serial break will drop to ddb. From there you could do 'call boot(0)'
> to attempt and orderly shutdown, or 'reset' to, well, reset :)
> There's also an 'ALT_BREAK_TO_DEBUGGER' option that emulates the sun
> alt-break -- [cr] ~ ^B.

btw - DDB in 5.* has a "reset" command so you don't have to remember
"call boot(0)".  It runs "cpu_reset" to immediately reset the system. 
Calling "boot(0)" has a better chance of doing a clean reboot but if
you're already locked up it may hang as well.

-- 
	Dan Nelson
	dnelson@allantgroup.com