*BSD News Article 48938


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!swidir.switch.ch!univ-lyon1.fr!news-rocq.inria.fr!news2.EUnet.fr!EU.net!newsfeed.internetmci.com!news.sprintlink.net!cs.utexas.edu!uwm.edu!src.honeywell.com!recnews-2.4
From: englehar@src.honeywell.com (Matt Englehart)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: HELP, PLEASE! pc locks up when doing file transfer over serial port
Date: 17 Aug 1995 07:14:52 -0500
Organization: mailEnteringNews @ Honeywell Technology Center
Lines: 26
Sender: daemon@src.honeywell.com
Message-ID: <9508171214.AA00615@johnwayne.src.honeywell.com>
NNTP-Posting-Host: moon.src.honeywell.com
X-Received: from johnwayne.src.honeywell.com by moon.src.honeywell.com (4.1/smail2.6.3/SRCv0.25);
	Thu, 17 Aug 95 07:14:49 CDT id AA12121  for comp.unix.bsd.freebsd.misc  at 
Posted-Date: Thu, 17 Aug 95 07:14:47 CDT
Received-Date: Thu, 17 Aug 95 07:14:49 CDT
X-Received: by johnwayne.src.honeywell.com (4.1/SMI-3.2)
	id AA00615; Thu, 17 Aug 95 07:14:47 CDT
X-To: comp.unix.bsd.freebsd.misc

Hi, this problem is on a critical path for me.  If you have anything to 
offer, I'd really appreciate it.

I'm running the April snapshot of 2.0 on a pc that is hooked up to a
network with the 3com 509b board.  When I attempt to do a file transfer
over the serial port, the machine hangs.  Sometimes I get a warning: messages
saying the silo buffer is overflowwing (I have a UART16550A).  I am
connceting with a 28800 modem, and between the pc and the modem I have
tried 38400 and 115200.  This happens when I try transfering a file using
any of the following applications:

1. netscape over ppp
2. ftp over ppp
3. rz/sz
4. tupload over term (the term program, originally written for Linux)

It seems as though things have gotten worse now that I've added the
ethernet interface.  It used to rarely hang.  Now it does within an instant
of attempting file transfer.

I'm thinking of trying out 2.0.5R.  Do you have enough of a clue as to what
the problem might be to say that it might be eliminated in 2.0.5R?

Thanks,

Matt Englehart