Debugging CAM_REQ_CMP_ERR errors / bulk transfer failures

[Shrikanth Kamath]

Thanks for the response Hans, the same issue was seen with another
vendor (the other device was Kingston Data Traveller)

umass1: Kingston DataTraveler 2.0, rev 2.00/1.00, addr 3
umass1: SCSI over Bulk-Only; quirks = 0x0000

These were the logs seen with Kingston

umass1: Invalid CSW: sig 0x43425355 should be 0x53425355
g_vfs_done():da1s3e[WRITE(offset=14123008, length=131072)]error = 5
...
umass1: Invalid CSW: sig 0x43425355 should be 0x53425355
usbd_transfer_cb: short transfer 28672<65536
...
initiate_write_filepage: already started
umass1: BBB reset failed, TIMEOUT
umass1: BBB reset failed, TIMEOUT
g_vfs_done():da1s3e[WRITE(offset=8192, length=2048)]error = 5
panic: initiate_write_inodeblock_ufs1: already started
...

Could this be firmware related too? Can any quirks be added for this?

Thanks,
--
Shrikanth R K

On Mon, Aug 24, 2015 at 12:30 AM, Hans Petter Selasky <hp at selasky.org> wrote:
> On 08/24/15 09:25, Shrikanth Kamath wrote:
>>
>> umass0: BBB reset failed, IOERROR
>> umass0: BBB bulk-in clear stall failed, IOERROR
>> umass0: BBB bulk-out clear stall failed, IOERROR
>
>
> This means your USB HDD is no longer responding. Maybe a USB re-enumeration
> will help, though then you will loose the disk. Possible USB firmware
> bug/race.
>
> --HPS