From owner-freebsd-hackers  Mon Nov  3 12:29:50 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA00838
          for hackers-outgoing; Mon, 3 Nov 1997 12:29:50 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA00826
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 3 Nov 1997 12:29:44 -0800 (PST)
          (envelope-from henrich@crh.cl.msu.edu)
Received: (from henrich@localhost)
	by crh.cl.msu.edu (8.8.5/8.8.5) id PAA23957;
	Mon, 3 Nov 1997 15:29:19 -0500 (EST)
Message-ID: <19971103152919.12038@crh.cl.msu.edu>
Date: Mon, 3 Nov 1997 15:29:19 -0500
From: Charles Henrich <henrich@crh.cl.msu.edu>
To: Don Lewis <Don.Lewis@tsc.tdk.com>
Cc: Matt Thomas <matt@3am-software.com>, Jaye Mathisen <mrcpu@cdsnet.net>,
        freebsd-hackers@FreeBSD.ORG
Subject: Re: de0 errors
References: <henrich@crh.cl.msu.edu> <199710280046.QAA23849@salsa.gv.tsc.tdk.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84
In-Reply-To: <199710280046.QAA23849@salsa.gv.tsc.tdk.com>; from Don Lewis on Mon, Oct 27, 1997 at 04:46:03PM -0800
X-Operating-System: FreeBSD 2.2.2-RELEASE
X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF  76 C4 B8 C9 6E 41 A4 4F
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On the subject of Re: de0 errors, Don Lewis stated:

> A PCI bus analyzer could be useful if the problem is what I think it is.
> What processor and PCI chipset do you have?

This is an ALR Revolution MP-Pro system w/ 1 200Mhz PPro, 256MB Ram, 4 SCSI
Cards, a Video card, and a SMC Etherpower 10/100 Card.  Its an Intel 440FX
chipset..

> > Just using FTP between two hosts on the 100mbit net I see 2-3MB/sec and
> > receive at about half that.
> 
> That's not very impressive.  To eliminate the influence of disk I/O, you
> might want to test network throughput using ttcp or something similar.  I'd
> recommend using ping to check for packet loss at the same time.  You
> shouldn't see any packet loss if you're sending between two machines on the
> same network segment.
> 

Humm, tcpblast shows 4.0MB/sec.  Granted this isnt an empty net either, fairly
busy I would imagine.  

-Crh

       Charles Henrich     Michigan State University     henrich@msu.edu

                         http://pilot.msu.edu/~henrich