*BSD News Article 78335


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!psgrain!iafrica.com!uct.ac.za!quagga.ru.ac.za!howland.erols.net!cam-news-hub1.bbnplanet.com!news.mathworks.com!newsfeed.internetmci.com!in3.uu.net!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!uknet!yama.mcc.ac.uk!ip
From: ip@mcc.ac.uk (Ian Pallfreeman)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 2.2-CURRENT sio silo overflow (was: Re: 2.1.5-RELEASE sio silo overflows?)
Date: 14 Sep 1996 21:56:21 GMT
Organization: not this decade...
Lines: 42
Message-ID: <51f9m5$jo3@yama.mcc.ac.uk>
References: <50i54c$mq7@yama.mcc.ac.uk> <512goo$15q@anorak.coverform.lan> <gergDxK0FH.AFp@netcom.com> <51a8vo$nre@godzilla.zeta.org.au>
NNTP-Posting-Host: albatross.mcc.ac.uk

In article <51a8vo$nre@godzilla.zeta.org.au>,
Bruce Evans <bde@zeta.org.au> wrote:
>These numbers show that the default FIFO trigger level of 14 is adequate
>for one or two 16550 ports on a 486/33 or faster machine, 

I've just spent about 2 days supping 2.2-CURRENT over a length of wet string
stretching from Manchester UK to Washington and back to Aachen DE. I suppose
I should be grateful that Mr. Nynex still hasn't charged me for the phone 
calls to my ISP, but I'm still being plagued by these damned silo overflows.

	FreeBSD 2.2-CURRENT (CLOVER) #0: Sat Sep 14 21:30:33 BST 1996

	sio0: disabled, not probed.
	sio1 at 0x2f8-0x2ff irq 3 on isa
	sio1: type 16450
	sio2 at 0x3e8-0x3ef irq 4 on isa
	sio2: type 16550A
	sio3: disabled, not probed.

	Sep 14 22:18:25 clover /kernel: sio2: 1 more silo overflow (total 2)

Poor little clover is a humble 486-DX2/66 with an Adaptec 2842 VLB SCSI 
controller. The overflows are triggered by disk access, but not by poking
the tape drives. The 16550s are on an ISA add-on card. I'm using dip & SLIP,
and the 28.8 modem is talking at 38.4. Up until I started on this unexpectedly
slippery slope, I'd been running Linux 1.2 for months with no signs of a
problem, but I've switched to FreeBSD since it's what I'm pushing as the
superior OS at University, where I have a whole bunch of machines running
quite happily. 

I've tried changing the fifo trigger from 14 to 8 in 2.1.5-RELEASE; that
improves things but still isn't perfect. I've supped 2.1.5-STABLE in the 
hope of discovering a fix. And now I'm jumping through the hoops finding
things needing to be recompiled for 2.2-CURRENT... this is driving me 
crazy! 

Ian.
-- 
 UNIX sysadmindroid, mail and news hacker, sentenced to a lifetime of slavery.
   Network Unit, Manchester Computing, The University, Manchester, England.
	  {ip@mcc.ac.uk,ip@u-net.com} -- http://jumper.mcc.ac.uk/~ip/
		Look before you leap; he who hesitates is lost.