Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@toe.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] help: what is "com0: silo overflow" error?
Date: 26 Nov 92 18:07:04
Organization: Kernel Hackers 'r' Us
Lines: 20
Message-ID: <CGD.92Nov26180704@toe.CS.Berkeley.EDU>
References: <84358@ut-emx.uucp> <CGD.92Nov26174908@toe.CS.Berkeley.EDU>
NNTP-Posting-Host: toe.cs.berkeley.edu
In-reply-to: cgd@toe.CS.Berkeley.EDU's message of 26 Nov 92 17:49:08
In article <CGD.92Nov26174908@toe.CS.Berkeley.EDU> cgd@toe.CS.Berkeley.EDU (Chris G. Demetriou) writes:
[ entire contents of my post deleted! ]
<sigh> it occurs to me that i didn't even answer your question... 8-)
the "com0: silo overflow" message occurs when two characters
are received by the UART before the first can be read.
That is "com0: silo overflow" means that the os couldn't
pull characters out of the uart fast enough, and so incoming data
was lost...
that's why your zmodem xfers are going so slow... 8-)
Chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"Sometimes it is better to have twenty million instructions by
Friday than twenty million instructions per second." -- Wes Clark