From owner-freebsd-current Wed Oct 9 14:49:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09253 for current-outgoing; Wed, 9 Oct 1996 14:49:16 -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 OAA09243 for ; Wed, 9 Oct 1996 14:49:11 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA10630; Wed, 9 Oct 1996 14:49:10 -0700 Date: Wed, 9 Oct 1996 14:49:09 -0700 (PDT) From: "Brian N. Handy" To: current@FreeBSD.org Subject: Re: SIO problems In-Reply-To: <23265.844891474@time.cdrom.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > [SIO overflow problems from Nate] Jordan: >Strange - my ISDN gateway box (which just uses at TA at 115.2Kb, so >there's a lot of traffic) is a 2.1.5 box and it's worked just fine >ever since the upgrade - no overflows at all with my 16550A UART. My PC's back at school (running unspecified 16450's on the mouse port) get these all the time, and my 6-month-old rgrimes P-133 has gotten these fairly routinely in the past. I haven't payed attention since the 960801 snap, though. Not sure where I stand right now. Brian