From owner-freebsd-bugs Wed Apr 4 4:10: 7 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0465D37B72B for ; Wed, 4 Apr 2001 04:10:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f34BA3R75890; Wed, 4 Apr 2001 04:10:03 -0700 (PDT) (envelope-from gnats) Date: Wed, 4 Apr 2001 04:10:03 -0700 (PDT) Message-Id: <200104041110.f34BA3R75890@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: i386/26261: silo overflow problem in sio driver Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/26261; it has been noted by GNATS. From: Bruce Evans To: Rich Wales Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: i386/26261: silo overflow problem in sio driver Date: Wed, 4 Apr 2001 21:02:24 +1000 (EST) On Tue, 3 Apr 2001, Rich Wales wrote: > WATANABE Kiyoshi wrote: > > > try this patch. > > + cp4ticks *= 10; /* to avoid buffer overflow */ > > Thanks. This helped to some extent, though I'm still seeing some > silo overflows even with the above patch. Should the "10" be bumped > up to something larger, perhaps? This can't possibly help reduce silo overflows, since it increases the size a driver buffer, but silo overflows occur when a hardware buffer is too small. Silo overflows are caused by non-sio hardware hogging the bus or by interrupt latency outside the driver. They should never occur at low speeds like 115200 bps even on 386/20's (except in -current, where interrupt latency outside the driver is certainly broken enough to matter even on 486DX2/66's). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message