From owner-freebsd-sparc64@FreeBSD.ORG  Mon Jul 21 13:37:49 2003
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2678637B401
	for <freebsd-sparc64@freebsd.org>;
	Mon, 21 Jul 2003 13:37:49 -0700 (PDT)
Received: from collab.or8.net (collab.or8.net [209.94.128.81])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AA52F43F93
	for <freebsd-sparc64@freebsd.org>;
	Mon, 21 Jul 2003 13:37:48 -0700 (PDT)
	(envelope-from cjacksorrynospam@klatsch.org)
Received: by collab.or8.net (Postfix, from userid 1002)
	id 35D0C5310; Mon, 21 Jul 2003 16:37:48 -0400 (EDT)
Date: Mon, 21 Jul 2003 16:37:48 -0400
From: Chris Jackman <cjacksorrynospam@klatsch.org>
To: freebsd-sparc64@freebsd.org
Message-ID: <20030721203748.GB42900@collab.or8.net>
References: <20030721194436.GA42900@collab.or8.net>
	<20030721202630.GA21283@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030721202630.GA21283@dragon.nuxi.com>
User-Agent: Mutt/1.4.1i
Subject: Re: correctable DMA error AFAR
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2003 20:37:49 -0000

On Mon, Jul 21, 2003 at 01:26:30PM -0700, David O'Brien wrote:
> On Mon, Jul 21, 2003 at 03:44:36PM -0400, Chris Jackman wrote:
> > Also, is there a way to send a break over the serial console? 
> > I can send it with cu using ~#, but the e250 doesn't respond
> > to it.  My guess is that it is a solaris feature to catch
> > the break signal, and drop to the Openboot Firmware.  
> 
> Sun's will only respond to <BREAK> while Openboot is in control (ie, from
> power on until the OS boot loader is run).  Your e250 should respond to
> <BREAK> during the memory count(check) for instance.

I think I use the wrong words.

When I boot solaris, I can send a <BREAK> using ~#, and 
it'll give me an "{0} ok" prompt.  I can type "go" to get 
back to solaris, or reset/etc.

I can't do that with freebsd.  

Is that a solaris feature, or an Openboot feature ?

If a ctrl-alt-esc is not the same as a <BREAK> (~# in cu), how do i 
send a ctrl-alt-esc over the serial console to drop into the debugger
when my scrolling "correctable error" floods the serial console. =)

(because from the debugger, i'm guessing i can use 'call cpu_reset' 
to reboot the machine over the serial console.  if i could get to the
openboot, i could use reset to reboot the machine over the serial console.
either way works for me, but i figured if i could get into the debugger,
i might be able to get some helpful information.)

Thanks for replying!