From owner-freebsd-usb@FreeBSD.ORG Sat Sep 1 16:40:57 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 DBC1B16A419 for ; Sat, 1 Sep 2007 16:40:57 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE2913C478 for ; Sat, 1 Sep 2007 16:40:57 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l81GdtHb083446; Sat, 1 Sep 2007 10:39:55 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 01 Sep 2007 10:39:59 -0600 (MDT) Message-Id: <20070901.103959.756905620.imp@bsdimp.com> To: wmoran@potentialtech.com From: "M. Warner Losh" In-Reply-To: <20070901094702.2a98a565.wmoran@potentialtech.com> References: <20070901094702.2a98a565.wmoran@potentialtech.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 01 Sep 2007 10:39:55 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: 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 16:40:57 -0000 In message: <20070901094702.2a98a565.wmoran@potentialtech.com> Bill Moran writes: : : 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? We need to quirk it... We should be smarter about this... Warner