From owner-freebsd-stable  Fri Sep 19 17:50:10 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA22106
          for stable-outgoing; Fri, 19 Sep 1997 17:50:10 -0700 (PDT)
Received: from gaylord.async.vt.edu (gaylord.async.vt.edu [128.173.18.131])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22101
          for <freebsd-stable@freebsd.org>; Fri, 19 Sep 1997 17:50:05 -0700 (PDT)
Received: (from gaylord@localhost)
	by gaylord.async.vt.edu (8.8.5/8.8.5) id UAA02854;
	Fri, 19 Sep 1997 20:45:56 -0400 (EDT)
From: Clark Gaylord <gaylord@gaylord.async.vt.edu>
Message-Id: <199709200045.UAA02854@gaylord.async.vt.edu>
Subject: Re: silo overflows...
In-Reply-To: <199709171730.KAA00227@netcom1.netcom.com> from "Michael V. Harding" at "Sep 17, 97 10:30:41 am"
To: mvh@netcom.com (Michael V. Harding)
Date: Fri, 19 Sep 1997 20:45:55 -0400 (EDT)
Cc: ceharris@vt.edu (Carl Harris), freebsd-stable@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Mike --

Well, I just moved my modem to sio2.  Fired up X, did a bunch of
'scaping, ftpin, and X/Tk stuff and no silo overflows.  I think we
may have a weiner.

Hope you have similar luck. ... and that mine holds :-)

Clark Gaylord

> It's possible that we have a similar situation.  I'm running a generic
> S3 Virge chip, but my modem is on sio2.  The silo overrun can happen
> when there is a long interrupt latency - and the S3 drivers may be
> disabling interrupts.  Not in general a problem.  I moved my modem
> connect to 56K and most of my problems have gone away, although this
> is just a bandaid.
> 
> I am, however, having video artifacts, which I never used to have.
> Gargh.
> 
> Thanks for your input,
> 
> Mike Harding
> 
>    From: Clark Gaylord <gaylord@gaylord.async.vt.edu>
>    Date: Wed, 17 Sep 1997 00:22:26 -0400 (EDT)
>    X-Mailer: ELM [version 2.4ME+ PL31 (25)]
>    MIME-Version: 1.0
>    Content-Type: text/plain; charset=US-ASCII
>    Content-Transfer-Encoding: 7bit
>    X-UIDL: da785a37a99dab659b933b8fbfbebca9
> 
>    I have seen this a lot w/ 2.2.1+, but the problem seems to only happen
>    to me when I run X.  So long as I do everything in telnet/vtty, all is
>    fine.  My setup is:
>       Mylex MTI386 (DX33)
>       Adaptec 1542
>       Diamond Stealth24
>       28.8 external modem
>       serial mouse
> 
>    I experience occassional mouse com port silo overflows and lots (hundreds)
>    of modem cort silo overflows.  I changed my serial port twice, and nothing
>    worked.  The other factoid I uncovered recently is possible incompatibilities
>    between sio3 and S3 video chipsets.  I have not moved modem to sio2, though
>    this is something I plan to do.
> 
>    In general, though, silo overruns indicate interupt conflicts, faulty 
>    hardware, don't they?
> 
>    -- 
>    Clark K. Gaylord
>    Blacksburg, Virginia USA
>    cgaylord@vt.edu
>    gaylord@usit.net
> 
>    > I don't know if this is a 'stable' question, but I am getting silo
>    > overflows after upgrading to a K6 / Asus TX-97 combo and upgrading to
>    > -stable.  Is there something different about this setup?  Should I
>    > turn off bus mastering?  Anyone else seen this?  I would be surprised
>    > if the TX chipset was messed up.
>    > 
>    > Also, how do I turn down the threshold in sio.c?  I looked at the code
>    > but wasn't able to determine what to hack to set the threshold to 8
>    > bytes.
>    > 
>    > Thanks!
>    > 
>    > Mike Harding
>    > 
>    > 
>    > 
> 
> 
> 
> 
> 


-- 
Clark K. Gaylord
Blacksburg, Virginia USA
cgaylord@vt.edu
gaylord@usit.net