From owner-freebsd-usb@FreeBSD.ORG Sat Sep 1 14:40:38 2007 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 BDF5816A417 for ; Sat, 1 Sep 2007 14:40:38 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 7458A13C45A for ; Sat, 1 Sep 2007 14:40:38 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id 04AB0EBC78 for ; Sat, 1 Sep 2007 09:47:02 -0400 (EDT) Date: Sat, 1 Sep 2007 09:47:02 -0400 From: Bill Moran To: freebsd-usb@freebsd.org Message-Id: <20070901094702.2a98a565.wmoran@potentialtech.com> X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Problems accessing "Digital Hero 3" camera (BBB * STALLED errors) 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: Sat, 01 Sep 2007 14:40:38 -0000 Recently acquired a GoPro "Digital Hero 3" digicam. It's got a USB interface and allegedly presents itself as a umass device. When I connect it, I get the following: Sep 1 09:25:57 working kernel: umass0: ZORAN COACH DSC, rev 1.10/0.00, addr 2 Sep 1 09:25:57 working kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Sep 1 09:25:57 working kernel: da0: Removable Direct Access SCSI-0 device Sep 1 09:25:57 working kernel: da0: 1.000MB/s transfers Sep 1 09:25:57 working kernel: da0: 982MB (2012160 512 byte sectors: 64H 32S/T 982C) Sep 1 09:25:57 working kernel: umass0: Phase Error, residue = 0 Sep 1 09:25:57 working kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Sep 1 09:26:07 working kernel: umass0: BBB reset failed, STALLED Sep 1 09:26:07 working kernel: umass0: BBB bulk-in clear stall failed, STALLED Sep 1 09:26:07 working kernel: umass0: BBB bulk-out clear stall failed, STALLED The device is inaccessible. I'm able to access it if I reboot to Linux, so the device isn't _completely_ broken. Some google searches turn up similar problems with other USB umass devices that seem to be universally solved by adding quirks to scsi_da.c. Is this the only way to fix this? I know terribly little about USB architecture, but it seems ugly to have to add a quirk for every single johnny-come-lately USB device that emulates umass poorly. I went looking to see if there were any sysctls to tweak, but have yet to find any. Should I file a PR to have a quirk added, or am I missing something? uname -a FreeBSD working.potentialtech.com 6.2-RELEASE-p5 FreeBSD 6.2-RELEASE-p5 #0: Sun May 27 00:53:14 EDT 2007 wmoran@working.potentialtech.com:/usr/obj/usr/src/sys/GENERIC i386 -- Bill Moran http://www.potentialtech.com