From owner-freebsd-usb@FreeBSD.ORG Thu Mar 19 19:31:23 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED06A10656CA for ; Thu, 19 Mar 2009 19:31:23 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 590D58FC1A for ; Thu, 19 Mar 2009 19:31:23 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A424E.dip.t-dialin.net [84.154.66.78]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id n2JJVEDA077897; Thu, 19 Mar 2009 20:31:15 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id n2JJVlCI093965; Thu, 19 Mar 2009 20:31:47 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n2JJVamf061503; Thu, 19 Mar 2009 20:31:47 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200903191931.n2JJVamf061503@fire.js.berklix.net> To: freebsd-usb@freebsd.org From: "Julian Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://berklix.com In-reply-to: Your message "Thu, 19 Mar 2009 11:13:29 +0100." <200903191013.n2JADT9T054996@fire.js.berklix.net> Date: Thu, 19 Mar 2009 20:31:36 +0100 Sender: jhs@berklix.org Cc: Subject: Re: Belkin Cardbus USB2 adaptors too hot. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2009 19:31:24 -0000 Problem solved :-) All hangs I mentioned till now were coming from 2 identical enclosures I have, they report as: vendor=0x058f product=0x6390 devclass=0x00 devsubclass=0x00 release=0x0100 sernum="" intclass=0x08 intsubclass=0x06 2 other enclosures of different ID I have are OK. Should we extend devd or BSD USB code to issue a brief warning when devices match any in a lookup list of suspect rogues ? (Not the first flakey USB device I've encountered, Some Sony 2G sticks were bad, all 4, ( "vendor" "0x10d6"; "product" "0x1100"; "devclass" "0x00"; "devsubclass" "0x00"; "release" "0x0100"; ) PS Thanks for you power etc advice Warner :-) Further backround before conclusion above: { I moved same new 250G disc in same enclosure to another 7.1-RELEASE tower PC with & without USB hub, & with a current doubler cable (ie to suck up to a 2nd 0.5A from 2nd socket if disk wants) testblock -v /mnt/tmp/bla1 stopped writing at 5G. /var/log/messages & console: umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, TIMEOUT g_vfs_done():da0a[WRITE(offset=65536, length=2048)]error = 5 g_vfs_done():da0a[WRITE(offset=6144000, length=16384)]error = 5 g_vfs_done():da0a[WRITE(offset=6160384, length=6144)]error = 5 g_vfs_done():da0a[WRITE(offset=198229819392, length=16384)]error = 5 .... I swapped the disc to a different USB to IDE converter, omitted case, disc does not get hot, but USB to IDE chip painfully hot (on good converter) + another power doubler cable, straight into PC, no hub, it wrote then read all remaining FS free space of 217 G succesfully. I swapped my other previously failing 120 G disc out of bad enclosure, into a known good enclosure, NO problems now on that either, have written 106 with no hang, & read verified 60 G as I type. } Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org