From owner-freebsd-bugs  Fri Nov  7 09:30:05 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA11453
          for bugs-outgoing; Fri, 7 Nov 1997 09:30:05 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA11439;
          Fri, 7 Nov 1997 09:30:01 -0800 (PST)
          (envelope-from gnats)
Date: Fri, 7 Nov 1997 09:30:01 -0800 (PST)
Message-Id: <199711071730.JAA11439@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Nate Williams <nate@mt.sri.com>
Subject: Re: kern/4968: Problems working with Courier I-Modem
Reply-To: Nate Williams <nate@mt.sri.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4968; it has been noted by GNATS.

From: Nate Williams <nate@mt.sri.com>
To: dgilbert@strike.velocet.ca
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/4968: Problems working with Courier I-Modem
Date: Fri, 7 Nov 1997 10:20:49 -0700 (MST)

 > >Number:         4968
 > >Category:       kern
 > >Synopsis:       No flow control setting seems to make the system happy
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Fri Nov  7 08:00:01 PST 1997
 > >Last-Modified:
 > >Originator:     David Gilbert
 > >Organization:
 > Velocet Communications
 > >Release:        FreeBSD 2.2.2-RELEASE i386
 > >Environment:
 > 
 > 	FreeBSD 2.2.2-RELEASE on a Pentium w/ a Courier I-Modem.  Courier
 > acts like serial port (internal modem).  Telix works properly.
 > 
 > >Description:
 > 
 > 	I have talked briefly about this problem once to one of the
 > developers.  Basically, if ctsrts is on cuaa2, the modem receives fine,
 > but cannot transmit large files (using ppp).  If ctsrts is off, sending
 > files is fine (this is counter intuitive, but my own feeble explaination
 > is that the card can control drain interupts), but receiving files will
 > only work for some period of time before the kernel starts spitting out:
 
 I suspect the remote site you are connecting to isn't using hardware
 flow control.  Both sides have to use hardware flow control, or else
 problems arise when one sides sends software flow control characters
 (^S/^Q).
 
 Make sure the remote site is using it, and all will be well.....
 
 
 
 Nate