From dgilbert@strike.velocet.ca  Fri Nov  7 07:58:13 1997
Received: from strike.velocet.ca (strike.velocet.ca [209.50.72.2])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA06390
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 7 Nov 1997 07:58:10 -0800 (PST)
          (envelope-from dgilbert@strike.velocet.ca)
Received: (from dgilbert@localhost)
	by strike.velocet.ca (8.8.7/8.8.7) id KAA27027;
	Fri, 7 Nov 1997 10:59:27 -0500 (EST)
Message-Id: <199711071559.KAA27027@strike.velocet.ca>
Date: Fri, 7 Nov 1997 10:59:27 -0500 (EST)
From: David Gilbert <dgilbert@strike.velocet.ca>
Reply-To: dgilbert@strike.velocet.ca
To: FreeBSD-gnats-submit@freebsd.org
Subject: Problems working with Courier I-Modem
X-Send-Pr-Version: 3.2

>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:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov  7 08:00:01 PST 1997
>Closed-Date:    Fri Mar 19 05:08:29 PST 1999
>Last-Modified:  Fri Mar 19 05:09:32 PST 1999
>Originator:     David Gilbert
>Release:        FreeBSD 2.2.2-RELEASE i386
>Organization:
Velocet Communications
>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:

Nov  7 03:16:24 wire1 /kernel: sio2: 54 more interrupt-level buffer overflows (total 788)
Nov  7 03:16:28 wire1 /kernel: sio2: 40 more interrupt-level buffer overflows (total 828)

	I do hate to drag you people into our own problems (esp after
the slight embarasment over the SCSI drive issue), but we've been
wrestling with this one for several months.

>How-To-Repeat:

	Connect Courier I-Modem to ISA bus, conffigure it for ppp,
send a big file (or recieve a big file, depending on ctsrts).

>Fix:
	
	

>Release-Note:
>Audit-Trail:

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

From: Bruce Evans <bde@zeta.org.au>
To: dgilbert@strike.velocet.ca, FreeBSD-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: kern/4968: Problems working with Courier I-Modem
Date: Tue, 11 Nov 1997 22:05:35 +1100

 >>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).
 
 I think you mean crtscts.  ctsrts is not an stty option.  Apparently
 rts flow control of input works, but cts flow control of output doesn't
 (because the modem doesn't support it or isn't configured to support it
 or is broken or the cable is broken...).
 
 >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:
 >
 >Nov  7 03:16:24 wire1 /kernel: sio2: 54 more interrupt-level buffer overflows (total 788)
 >Nov  7 03:16:28 wire1 /kernel: sio2: 40 more interrupt-level buffer overflows (total 828)
 
 This message is unusual.  It means that the system is overloaded with
 interrupt processing.  Apparently the modem can keep up without input
 flow control (into it), but FreeBSD can't.
 
 FreeBSD has separate options rtsflow and ctsflow for each direction of
 flow control, so you can use the one that works.
 
 Bruce
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Mar 19 05:08:29 PST 1999 
State-Changed-Why:  
Active development on the 2.2 branch is over. 
>Unformatted:
