Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!usenet.ucs.indiana.edu!bigbang.astro.indiana.edu!pitts From: pitts@bigbang.astro.indiana.edu (Jim Pitts) Subject: Problem with com ports and slip Message-ID: <CDrDup.GC5@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Nntp-Posting-Host: bigbang.astro.indiana.edu Organization: Indiana University Astrophysics, Bloomington, IN Date: Wed, 22 Sep 1993 14:06:15 GMT Lines: 39 Hi, I have a strange problem with NetBSD 0.9 running XFree86-1.3u1. I have an external 14.4K modem (USR Sporster). I WAS running it off of /dev/com1 (ie com2). I kept getting 'silo overflows' from that port. I assumed that this had something to do with my old communications board which is VERY old (but has always worked without a hitch). Well, I had been looking for a reason to buy a new board with a 16550A UART, so I went and did it. Need I say this had no effect? The new board has ONLY 2 serial ports on it, one with a 16550A and the other without (it drives the mouse). tip seems to work fine. Zmodem seems to produce a mesage like 'BAD CRC 0' followed by 'See man pages BUG chapter' (there is no such thing ... at least that I can find.) Slip seems to have the strangest problem. Originally with the old card the silo overflows were sending slip into the happy hunting grounds. It would just hang the conection. If sl0 was brought down, slattach killed, and sl0 brought back up again, all the IO that was waiting to come through would pour out. With the new card I see the same problem with slip. There is a new addition however. Everything seems to go fine. Then I do a 'telnet' out the port. I get connected, but aftert a few seconds telnet comes to a standstill. 'ping' still works well, as does ftp, but telnet seems to just sit there hung. Finally the whole system slowly grinds to a halt, ping times go to hell, etc. On the bright side the mouse works great! ;) Does anyone have any idea what might be going on? Thanks, Jim