Problems accessing "Digital Hero 3" camera (BBB * STALLED errors)

[M. Warner Losh]

In message: <20070901094702.2a98a565.wmoran at potentialtech.com>
            Bill Moran <wmoran at potentialtech.com> 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: <ZORAN COACH6 (I62) 1.10> 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