Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!news.mel.aone.net.au!grumpy.fl.net.au!news.webspan.net!www.nntp.primenet.com!nntp.primenet.com!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: tty overflow? Date: 18 Jan 1997 22:18:42 GMT Organization: Private BSD site, Dresden Lines: 23 Message-ID: <5bri82$30b@uriah.heep.sax.de> References: <5baffq$in8@seagoon.newcastle.edu.au> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34208 oumjm@alinga.newcastle.edu.au (MCLEOD M J) wrote: > I'm in the process of setting up our new server (FreeBSD 2.1.6), > and I noticed that quite a few "tty overflow" errors are being > generated (even while doing simple stuff like dialing out with > minicom). What `tty overflows'? There are two kinds: interrupt-level and buffer-level overflows. The first means that an interrupt has not been processed in due time. It's often the result of driving a line at high speed without using RTS/CTS (``hardware'') flow control. The second means that the interrupt routine was able to fetch all the bytes from the UART and stuff them into tty buffers, but the upper layers of the kernel were too busy to postprocess them. Solving this is often more complicated. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)