Test Results

[Julian Elischer]

On 5/26/14, 2:16 PM, Hans Petter Selasky wrote:
> On 05/26/14 05:16, Ronald F. Guilmette wrote:
>> 2)  As can be seen in the "desktop2-varlogmessages.txt' log file, 
>> on that
>> one system there were also a number of additional errors logged 
>> after the
>> Hitachi Touro Mobile drive was plugged in:
>>
>>      (probe0:umass-sim2:2:0:0): INQUIRY. CDB: 12 00 00 00 24 00
>>      (probe0:umass-sim2:2:0:0): CAM status: CCB request completed 
>> with an error
>>      (probe0:umass-sim2:2:0:0): Retrying command
>>      (probe0:umass-sim2:2:0:0): INQUIRY. CDB: 12 00 00 00 24 00
>>      (probe0:umass-sim2:2:0:0): CAM status: CCB request completed 
>> with an error
>>      (probe0:umass-sim2:2:0:0): Retrying command
>>      (probe0:umass-sim2:2:0:0): INQUIRY. CDB: 12 00 00 00 24 00
>>      (probe0:umass-sim2:2:0:0): CAM status: CCB request completed 
>> with an error
>>      (probe0:umass-sim2:2:0:0): Retrying command
>
> Hi,
>
> This error is typical for no-synchronize-cache.
>
> 1)
> Lookup the device above using "usbconfig".
>
> 2)
> Add the quirk, where X.Y are the numbers after "ugen".
> usbconfig -d X.Y add_quirk UQ_MSC_NO_SYNC_CACHE
>
> 3)
> Replug this device.

I've seen this pattern a bit too much.

  user: I see error X
  dev:   turn on quirk Y, disabling {lock device, queuing, syncing, 
block erase, etc.}


Would it be possible for part of the attach code for drives, to silently
run through a bunch of these commands and just turn off those that
return errors? In the Old (old) SCSI code we did this in some devices,
and in some cases there were capability descriptions in some of the 
sense pages.

(though I think that was on some proprietary subdrivers).

>
> --HPS
>
>
> _______________________________________________
> freebsd-usb at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
> To unsubscribe, send any mail to "freebsd-usb-unsubscribe at freebsd.org"
>
>