From owner-freebsd-hackers  Wed Aug 14 12:26:15 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA21312
          for hackers-outgoing; Wed, 14 Aug 1996 12:26:15 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA21306;
          Wed, 14 Aug 1996 12:26:09 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA00909; Thu, 15 Aug 1996 05:21:28 +1000
Date: Thu, 15 Aug 1996 05:21:28 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199608141921.FAA00909@godzilla.zeta.org.au>
To: handy@sag.space.lockheed.com, msmith@atrad.adelaide.edu.au
Subject: Re: sio issues (silo overflows on a pentium, locked in ttywait, etc...)
Cc: freebsd-hackers@freefall.freebsd.org, ponds!rivers@dg-rtp.dg.com,
        ponds!rivers@freefall.freebsd.org
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Now, it's worth noting that before I upgraded the 486 with the errant
>mouse port to...oh...I think 2.1?  (Nate would remember, he sees the same
>thing) I never got the "sio overflow" message in my syslogs.  Something
                         silo (no relation)
>has changed to make this error show up.  Again, I've never noticed it
>affecting anything.

>I don't remember when it started, so don't quote me on that.  It's a new
>development in the last 1.5 years or so though.

It didn't show up because of a bug in the error reporting.

Bruce