From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 26 14:04:28 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8765106566C; Mon, 26 Oct 2009 14:04:28 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 15A2A8FC29; Mon, 26 Oct 2009 14:04:27 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=7Qk2ozbKAAAA:8 a=3DEoRG9pZ8O1rmRWK4MA:9 a=amle3YBhDP2cSjTdLwkA:7 a=xZ_KKcwNocfnZFU_dISHYZDrLaEA:4 a=cvZW9r6VXHAA:10 a=HB4-cm7let6mbyM0:21 a=ifyaD4XHMZ9D0NMm:21 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1225145395; Mon, 26 Oct 2009 15:04:26 +0100 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Mon, 26 Oct 2009 15:03:33 +0100 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200910261258.08135.hselasky@c2i.net> <86skd6cmm8.fsf@ds4.des.no> <20091026.073759.2130803790.imp@bsdimp.com> In-Reply-To: <20091026.073759.2130803790.imp@bsdimp.com> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpO< =?iso-8859-1?q?Q0yAl=7E=3F=60=27F=3FjDVb=5DE6TQ7=27=23h-VlLs=7Dk/=0A=09?=(yxg(p!IL.`#ng"%`BMrham7%UK,}VH\wUOm=^>wEEQ+KWt[{J#x6ow~JO:,zwp.(t; @ =?iso-8859-1?q?Aq=0A=09=3A4=3A=26nFCgDb8=5B3oIeTb=5E=27?=",; u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200910261503.33747.hselasky@c2i.net> Cc: des@des.no, freebsd-usb@freebsd.org Subject: Re: Help troubleshooting... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2009 14:04:28 -0000 On Monday 26 October 2009 14:37:59 M. Warner Losh wrote: > In message: <86skd6cmm8.fsf@ds4.des.no> > > Dag-Erling_Sm=F8rgrav writes: > : "M. Warner Losh" writes: > : > FreeBSD lighthouse 9.0-CURRENT FreeBSD 9.0-CURRENT #41 r185338:198411= M: > : > Fri Oct 23 10:08:48 MDT 2009 =20 > : > imp@lighthouse:/cache/svn/head/sys/amd64/compile/LIGHTHOUSE amd64 > : > > : > so it would have r197682 baked in (the first number in my rev string > : > is a mystery to me). > : > : It means you have an inconsistent tree. The first number is the oldest > : revision in your tree, the second is the newest, and the M means you > : have local modifications. > > Yes. Of course I have local modifications, but none in the usb stack. > But I've also done a svn update from the top of the tree multiple > times and this version number persists. > > : > Re another post: This is a 8GB flash, so I'm sure that there's enough > : > power. > : > : Non sequitur. Bigger chips draw more power. Is it plugged directly > : into the computer? If not, is it plugged into a powered hub? How many > : other devices are connected to the computer or hub? > Hi, > Not entirely. This flash has worked in this computer in the past > without issues (like a year ago when we were first integrating hpsusb > into the tree). Since then there has been at least one patch to improve performance in the= =20 EHCI driver. When the cat command stops, could you try to run: usbconfig -u XXX -a YYY dump_device_desc dump_curr_config_desc On that device. Is usbconfig able to extract the string descriptors in the= =20 device and config descriptor? Or do you get timeouts? Also check vmstat -i . > This flash is plugged directly into the computer. > This behavior is consistent across multiple ports on the computer (so > it isn't a bad port). While this doesn't prove it isn't a power > issue, the odds are stacked against it being one. If there were a way > to get the internal hub to tell me how much power it can deliver, and > for me to query the flash to see maximum current draws, we could see > if we're close to the edge or not... Usually the maximum current is given by the device descriptor, but it might= =20 now be the actual value. See usbconfig dump_device_desc. =2D-HPS