Date: Thu, 3 Jan 2002 15:43:29 -0500 (EST) From: Mike Silbersack <silby@silby.com> To: Thomas Zenker <thz@Lennartz-electronic.de> Cc: <net@freebsd.org>, Josef Karthauser <joe@tao.org.uk>, Matthew Dillon <dillon@apollo.backplane.com> Subject: Re: USB ethernet problem Message-ID: <Pine.BSF.4.30.0201031518300.45843-100000@niwun.pair.com> In-Reply-To: <20020102170917.A8308@mezcal.tue.le>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.30.0201031518300.45843-100000>