From owner-freebsd-current  Fri Jun 18 12:46:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from xylan.com (postal.xylan.com [208.8.0.248])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0B14114D84; Fri, 18 Jun 1999 12:46:21 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT]))
	id MAA27989; Fri, 18 Jun 1999 12:45:44 -0700 (PDT)
Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB]))
	id MAA07634; Fri, 18 Jun 1999 12:45:45 -0700
Received: from softweyr.com (dyn2.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL]))
	id AA13732; Fri, 18 Jun 99 12:45:43 PDT
Message-Id: <376AA1E6.F529ED99@softweyr.com>
Date: Fri, 18 Jun 1999 13:45:42 -0600
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr LLC
X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386)
X-Accept-Language: en
Mime-Version: 1.0
To: Greg Lehey <grog@lemis.com>
Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG>,
	FreeBSD Hackers <hackers@FreeBSD.ORG>
Subject: Re: Remote serial gdb--status?
References: <19990618114450.Q9893@freebie.lemis.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Greg Lehey wrote:
> 
> I've been away from work for several weeks, and I now find that I can
> no longer start remote serial gdb.  I am using sio0 on the debugged
> machine side, and sio1 on the debugging machine side.  Here are the
> relevant dmesg outputs:
> 
> panic (debugged machine):
> 
> sio0: system console
> sio0: gdb debugging port
> ...
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0
> sio0: type 16550A
> 
> freebie (debugging machine):
> 
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> sio1: interrupting at irq 3
> 
> I can communicate fine using cu, and a breakout box shows all modem
> signals asserte (DCD, DTR, DSR, RTS, CTS).  When I go into remote
> debug on panic, RxD flashes, and when freebie tries to attach to
> panic, TxD flashes, so I'm obviously addressing the correct ports.
> I've checked the bit rate and configuration of the ports before going
> into debug, and they look right (9600 bps, cs8, -istrip, -parenb).  I
> don't know what else to look for.  Any ideas?

I think you need flags 0x50 (instead of 0x90) on panic.  From sio(4):

     Meaning of flags:
           ...
           0x00010   device is potential system console
           0x00020   device is forced to become system console
           0x00040   device is reserved for low-level IO (e. g. for remote
                     kernel debugging)
           ...

-- 
       "Where am I, and what am I doing in this handbasket?"

Wes Peters                                                 Softweyr LLC
http://www.softweyr.com/~softweyr                      wes@softweyr.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message