From owner-freebsd-hardware Mon Sep 15 09:42:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08293 for hardware-outgoing; Mon, 15 Sep 1997 09:42:24 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08288 for ; Mon, 15 Sep 1997 09:42:21 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA12987; Mon, 15 Sep 1997 09:38:38 -0700 (PDT) Date: Mon, 15 Sep 1997 09:38:38 -0700 (PDT) From: Jim Shankland Message-Id: <199709151638.JAA12987@biggusdiskus.flyingfox.com> To: jlixfeld@idirect.com Subject: Re: DLINK 21140 Card Cc: freebsd-hardware@freebsd.org Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From jlixfeld@idirect.com Mon Sep 15 06:04:06 1997 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Mon, 15 Sep 1997 09:07:35 -0400 (EDT) From: Jason Lixfeld To: Jim Shankland cc: freebsd-hardware@freebsd.org Subject: Re: DLINK 21140 Card In-Reply-To: <199709150503.WAA05355@biggusdiskus.flyingfox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jason Lixfeld writes: > I'm not sure if it will work or not, but I'm going to change it > to match TULIP_RXDESCS. That is set to 48. I'm not sure if it > will let me, or if it will even run. If you think not, let me > know. If I should change it to 32, should I not change RX to > 32 from 48 just to keep things symmetrical?! > > On Sun, 14 Sep 1997, Jim Shankland wrote: > > > Try reducing the value of TULIP_TXDESCS from 128 to 32, recompile the > > driver, and see if that helps; please report back either way. > > > > Jim Shankland > > Flying Fox Computer Systems, Inc. The important thing for the purpose of this experiment is to reduce the size of the tulip_softc structure to < 4 KB. The number of TXDESCS and RXDESCS need not be the same. When the size of the tulip_softc structure is > 4 KB, it is possible to see failures quite similar to what you are seeing. On the other hand, your problem might be entirely unrelated. Jim Shankland Flying Fox Computer Systems, Inc.