From owner-freebsd-hackers Tue Aug 13 22:48:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09548 for hackers-outgoing; Tue, 13 Aug 1996 22:48:53 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA09542; Tue, 13 Aug 1996 22:48:51 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA00531; Tue, 13 Aug 1996 22:48:44 -0700 Date: Tue, 13 Aug 1996 22:48:44 -0700 (PDT) From: "Brian N. Handy" To: Michael Smith Cc: Thomas David Rivers , sag.space.lockheed.com!handy@dg-rtp.dg.com, ponds!rivers@freefall.freebsd.org, freebsd-hackers@freefall.freebsd.org Subject: Re: sio issues (silo overflows on a pentium, locked in ttywait, etc...) In-Reply-To: <199608140601.PAA29529@genesis.atrad.adelaide.edu.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >The fact that you're the only person seeing this makes me wonder whether >you have funny serial hardware causing your problems. Note that lots of >PC serial hardware is _really_bad_, so this is actually fairly likely. > 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 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. Brian