From owner-freebsd-net Thu Jan 3 12:43:45 2002 Delivered-To: freebsd-net@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id D4A1C37B41D for ; Thu, 3 Jan 2002 12:43:29 -0800 (PST) Received: (qmail 63344 invoked by uid 3193); 3 Jan 2002 20:43:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Jan 2002 20:43:29 -0000 Date: Thu, 3 Jan 2002 15:43:29 -0500 (EST) From: Mike Silbersack X-Sender: To: Thomas Zenker Cc: , Josef Karthauser , Matthew Dillon Subject: Re: USB ethernet problem In-Reply-To: <20020102170917.A8308@mezcal.tue.le> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 2 Jan 2002, Thomas Zenker wrote: > Hi Mike, > > back from holidays... > > because this is now discussed in different threads, on -stable and > on -net, I will try to recapitulate what has happened and keep this > on -net "USB ethernet problem". > > The performance problems apeared after updating my test system from > 4.3 to 4.4 with Netgear EA101 USB/ethernet adaptor (kue driver). > Performance dropped by a factor of 10 or more. The server in all > cases was 4.4. After testing different slowstart flightsizes and > send/recv buffer sizes with ttcp the findings were, that mostly the > recvspace reduced to 16K (as in 4.3) recovered the performance. See > also my message to -stable from 2001/12/14. The usb host controller > on this system is a VIA 83C572 (UHCI). > > Now going to the final embedded hardware, the suprise was a hanging > usb driver. The strange thing is, this does not happen while testing > with ttcp, but only if the data is written to disk. The following > kernel messages are printed: > > usb0: host controller process error > usb0: host controller halted > kue0: watchdog timeout > kue0: usb error on tx: TIMEOUT > > this comes from uhci_intr() in dev/usb/uhci.c. Aparently the > usb0-messages reflect a hw status register!? This happens very > quickly with 4.4 (it is impossible to install over usb/ethernet), > but I have seen it today for the first time with 4.3 also. The usb > host controller is UHCI Intel 82371AB/EB (PIIX4). Well, since you've been able to isolate this as the cause, there's no need to run any more tcp tests with varying servers. Try changing hz, as I mentioned in the e-mail I just sent to you guys. Also, try running ttcp while seperately creating disk load (through a disk benchmark or something.) Meanwhile, watch systat -vm and see if the interrupt counts show you anything interesting. Thanks, Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message