Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site pucc-j
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!pucc-j!abe
From: abe@pucc-j (Vic Abell)
Newsgroups: net.unix,net.unix-wizards
Subject: Re: Telnet problems
Message-ID: <787@pucc-j>
Date: Thu, 6-Feb-86 09:03:45 EST
Article-I.D.: pucc-j.787
Posted: Thu Feb  6 09:03:45 1986
Date-Received: Fri, 7-Feb-86 21:23:30 EST
References: <134@gt-cmmsr.UUCP>
Reply-To: pur-ee!pucc-j!abe (Vic Abell)
Organization: Purdue University Computing Center
Lines: 23
Keywords: flow control, dmf32's
Xref: watmath net.unix:7038 net.unix-wizards:16681
Summary: really a dmf.c problem

In article <134@gt-cmmsr.UUCP> deb@gt-eedsp.UUCP (Deborah Jackson) writes:
>
>We have a very strange problem with our telnet program.  Our Vax 11/780
>is running 4.2BSD (BRL) UNIX(TM).
>. . .  Whenever invoked,
>either through our ethernet to our Data General or through the software
>loop-back to itself, it stops after a seemingly arbitrary number of 
>characters. . . 
>I've also never worked on a Vax with dmf32's before now, which leads me 
>to believe they are the culprit.

Yes, the problem is a missing selwakeup() call in dmfstart() of dmf.c.
One should be inserted after line 533 (approximately):

dmfstart(tp)
	.
	.
	.
		if (tp->t_wsel) {
=====>			selwakeup(tp->t_wsel, tp->t_state & TS_WCOLL);
			tp->t_wsel = 0;
			tp->t_state &= ~TS_WCOLL;
		}