From owner-freebsd-alpha@FreeBSD.ORG  Fri Sep 26 16:10:51 2008
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7EA27106568E
	for <freebsd-alpha@freebsd.org>; Fri, 26 Sep 2008 16:10:51 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from parsely.rain.com (parsely.rain.com [199.26.172.196])
	by mx1.freebsd.org (Postfix) with ESMTP id C4EE88FC2C
	for <freebsd-alpha@freebsd.org>; Fri, 26 Sep 2008 16:10:50 +0000 (UTC)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from sopwith.solgatos.com (uucp@localhost)
	by parsely.rain.com (8.11.4/8.11.4) with UUCP id m8QGAn464999
	for freebsd-alpha@freebsd.org; Fri, 26 Sep 2008 09:10:49 -0700 (PDT)
	(envelope-from freebsd@sopwith.solgatos.com)
Received: from localhost by sopwith.solgatos.com (8.8.8/6.24)
	id QAA12966; Fri, 26 Sep 2008 16:05:52 GMT
Message-Id: <200809261605.QAA12966@sopwith.solgatos.com>
To: freebsd-alpha@freebsd.org
In-reply-to: Your message of "Tue, 23 Sep 2008 10:00:09 GMT."
	<200809231000.m8NA092P013281@freefall.freebsd.org> 
Date: Fri, 26 Sep 2008 09:05:52 +0100
From: Dieter <freebsd@sopwith.solgatos.com>
Subject: Re: alpha/127248: System crashes when many (7) serial port
	terminals (vt320-vt510) connected to the server via com to
	usb adapter and 2-usb hubs. 
X-BeenThere: freebsd-alpha@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the Alpha <freebsd-alpha.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-alpha>
List-Post: <mailto:freebsd-alpha@freebsd.org>
List-Help: <mailto:freebsd-alpha-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2008 16:10:51 -0000

>  I didn't find out how to copy this to email and just retyped it here by
>  hands, so there maybe some mistakes, even though i was very careful.
>  How to do that btw?

For "normal" output, look in /var/log.  However, I assume the debugger
doesn't write to disk.  And neither does firmware.

One way is to connect the RS-232 console to a port on a second system,
and tip/cu from the second system into the problematic system.
You can then capture output using script(1).

IIRC, some "smart" terminals allow copy and paste.

I use the RS-232 port on an X terminal and use X11 copy and paste.

If all else fails you could take a photo of the screen.