Date: Sun, 27 Sep 2009 19:40:31 +0200 From: Hans Petter Selasky <hselasky@freebsd.org> To: Eugene Grosbein <eugen@kuzbass.ru> Cc: usb@freebsd.org Subject: Re: 8.0-RC1: AMD CS5536 (Geode) USB 2.0 controller strange behavour Message-ID: <200909271940.32878.hselasky@freebsd.org> In-Reply-To: <20090927161407.GA25879@svzserv.kemerovo.su> References: <20090926081733.GA24121@svzserv.kemerovo.su> <20090927143138.GA20842@svzserv.kemerovo.su> <20090927161407.GA25879@svzserv.kemerovo.su>
index | next in thread | previous in thread | raw e-mail
On Sunday 27 September 2009 18:14:08 Eugene Grosbein wrote: > On Sun, Sep 27, 2009 at 10:31:38PM +0800, Eugene Grosbein wrote: > > > %dd if=/dev/zero bs=64k of=/dev/da0 count=1000 > > > > > > It started to work, meantime iostat output was: > > > > > > 63.62 17 1.05 > > > 0.00 0 0.00 > > > 0.00 0 0.00 > > > 0.00 0 0.00 > > > 0.00 0 0.00 > > > 0.00 0 0.00 > > > 64.00 2 0.15 > > > 62.31 83 5.06 > > > 0.25 0 0.00 > > > 0.00 0 0.00 > > > 0.00 0 0.00 > > > ^C > > I've repeated the test with my USB flash drive formatted as FAT32. > It gives the same result: for ICH7-based system I get 26 megabyte/s > file writing speed and for AMD CS5536 it suffers from long periods of > inactivity while writing data, hence very low awarage writing speed. > > It seems the root of the problem is in the interaction > between USB stack and AMD CS5536 (Geode) USB 2.0 controller > and not in media devices themselves. > > Any more hints please? sysctl hw.usb.ehci.debug=15 If the USB stack puts the new job into the schedule and the USB controller does not pick it up, it is not an USB stack problem ... --HPShome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909271940.32878.hselasky>