From owner-freebsd-hardware Wed Oct 9 17:21:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA22240 for hardware-outgoing; Wed, 9 Oct 1996 17:21:31 -0700 (PDT) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA22230 for ; Wed, 9 Oct 1996 17:21:28 -0700 (PDT) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id RAA27026; Wed, 9 Oct 1996 17:19:19 -0700 Date: Wed, 9 Oct 1996 17:19:19 -0700 From: Jim Shankland Message-Id: <199610100019.RAA27026@saguaro.flyingfox.com> To: jas@flyingfox.COM, julian@whistle.com Subject: Re: Poor SMC Etherpower 10/100 transfer rates Cc: John.McLaughlin@acucobol.ie, hardware@FreeBSD.ORG, rgrimes@gndrsh.aac.dev.com Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From julian@whistle.com Wed Oct 9 17:05:27 1996 Return-Path: julian@whistle.com Received: (from smap@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id RAA26996 for ; Wed, 9 Oct 1996 17:05:26 -0700 Received: from alpo.whistle.com(207.76.204.38) by saguaro.flyingfox.com via smap (V1.3) id sma026994; Wed Oct 9 17:04:57 1996 Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id RAA21196; Wed, 9 Oct 1996 17:06:41 -0700 (PDT) Sender: julian@whistle.com Message-ID: <325C3D9B.446B9B3D@whistle.com> Date: Wed, 09 Oct 1996 17:04:43 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jim Shankland CC: John.McLaughlin@acucobol.ie, rgrimes@gndrsh.aac.dev.com, hardware@FreeBSD.ORG Subject: Re: Poor SMC Etherpower 10/100 transfer rates References: <199610092222.PAA26723@saguaro.flyingfox.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Status: R Julian Elischer wrote: > Jim Shankland wrote: > > > ballpark 3% of the theoretical maximum capacity); the FreeBSD > > box is reporting a 20%+ collision rate! I will now definitely > > try swapping out the SMC card. > > if it is reporting collisions then it's probably not teh culprit.. > it's the card that doesn't see ANY collisions thatyou should be > worried about. Hmm ... I wonder. I figure the card may be detecting collisions just fine, but "forgetting" to check for an idle wire before transmitting. In that case, it could transmit, then immediately detect a collision .... I'll be swapping out the SMC card tomorrow night, on general principle, and will report back if I find out anything interesting. Jim Shankland Flying Fox Computer Systems, Inc.