From owner-freebsd-net@FreeBSD.ORG  Tue May 18 16:50:52 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0475916A4CE
	for <freebsd-net@freebsd.org>; Tue, 18 May 2004 16:50:52 -0700 (PDT)
Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 54AD843D2D
	for <freebsd-net@freebsd.org>; Tue, 18 May 2004 16:50:49 -0700 (PDT)
	(envelope-from ernie@spooky.eis.net.au)
Received: (from ernie@localhost)
	by spooky.eis.net.au (8.12.11/8.12.11) id i4INKt2x019230
	for freebsd-net@freebsd.org; Wed, 19 May 2004 09:20:55 +1000 (EST)
	(envelope-from ernie)
From: User Ernie <ernie@spooky.eis.net.au>
Message-Id: <200405182320.i4INKt2x019230@spooky.eis.net.au>
To: freebsd-net@freebsd.org
Date: Wed, 19 May 2004 09:20:55 +1000 (EST)
X-Mailer: ELM [version 2.4ME+ PL99b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Subject: mgetty ppp stallion problem
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 May 2004 23:50:52 -0000

Something I have been meaning to post about but kept forgetting.

I have a FreeBSD 4.9-STABLE machine with a stallion card 
stl0: <EC8/32-PCI> port 0x7400-0x7403,0x7800-0x7807,0x8000-0x8003,0x8400-0x8407 irq 11 at device 12.0 on pci0
stl0: EC8/32-PCI (driver version 5.6.0b1) unit=0 nrpanels=1 nrports=16



It's acting as a modem server running mgetty+sendfax from the ports collection
MD5 (mgetty1.1.30-Dec16.tar.gz) = 4b80c418bc58add3e40de3be0ac6c02a

mgetty is set to spawn off a user ppp session which it does quite well, but 
every now and then when the caller hangs up the ppp session stays active so 
the serail port is unusable. If I do a kill on the ppp session the ppp
process dies but the sertial port on the stallion card does not free up and 
a reboot is required.

The megetty.config is as follows:

debug 6
data-only YES

 speed 57600
 port-owner uucp
 port-group network
 port-mode 0666
 toggle-dtr YES
 toggle-dtr-waittime 500
 direct NO
 blocking NO
 modem-type data
 init-chat "" ATS0=0Q0&D3&C1 OK
 modem-check-time 3600
 rings 2      
 answer-chat "" ATA CONNECT \c \r
 answer-chat-timeout 80 
 autobauding NO
 ringback NO
 ringback-time 30
 ignore-carrier false
 prompt-waittime 500
 login-prompt @!login: 
 login-time 240

It's almost as if ppp is not sending the right signal to release the serial 
port back to mgetty.

Any ideas?

- Ernie.