USB DataTraveller works but.

[Rowdy]

Rowdy wrote:
> Wojciech Puchar wrote:
> 
>> with lot of errors after i umount'ed dos filesystem
>>
>> Nov 29 12:00:35 chylonia kernel: umass1: Phase Error, residue = 0
>> Nov 29 12:00:35 chylonia kernel: (da4:umass-sim1:1:0:0): Synchronize 
>> cache failed, status == 0x4, scsi status == 0x0
>> Nov 29 12:00:35 chylonia kernel: umass1: Phase Error, residue = 0
>> Nov 29 12:00:35 chylonia kernel: sio4: 8 more silo overflows (total 50)
>> Nov 29 12:00:35 chylonia kernel: (da4:umass-sim1:1:0:0): Synchronize 
>> cache failed, status == 0x4, scsi status == 0x0
>> Nov 29 12:00:35 chylonia kernel: umass1: Phase Error, residue = 0
>> Nov 29 12:00:35 chylonia kernel: (da4:umass-sim1:1:0:0): Synchronize 
>> cache failed, status == 0x4, scsi status == 0x0
>> root at chylonia# Nov 29 12:00:35 chylonia kernel: umass1: Phase Error, 
>> residue = 0
>> Nov 29 12:00:35 chylonia kernel: (da4:umass-sim1:1:0:0): Synchronize 
>> cache failed, status == 0x4, scsi status == 0x0
> 
> 
> I have had similar problems, and a quick search revealed this:
> 
> http://lists.freebsd.org/pipermail/freebsd-bugs/2005-November/015744.html
> 
> That suggests to make a small change to scsi_da.c (in
> /usr/src/sys/cam/scsi) and presumably recompile the kernel.
> 
> I have not tried thisat yet (still trying to schedule an upgrade to 6.0
> - I intend to patch the file and recompile as part of the upgrade), but
> there are several references I found to suggest that it should work.
> 
> Rowdy

Before upgrading to 6.0 I patched scsi_da.c as described in the above 
link.  After everything settled down after the upgrade I plugged in the 
DataTraveler, and:

Dec  1 20:54:28 khaki kernel: umass0: vendor 0x0930 DataTraveler 2.0, 
rev 2.00/1.00, addr 2
Dec  1 20:54:30 khaki kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Dec  1 20:54:30 khaki kernel: da0: <Kingston DataTraveler 2.0 1.04> 
Removable Direct Access SCSI-0 device
Dec  1 20:54:30 khaki kernel: da0: 1.000MB/s transfers
Dec  1 20:54:30 khaki kernel: da0: 244MB (499712 512 byte sectors: 64H 
32S/T 244C)

At this point I was able to mount it and manipulate files.  Then I 
dismounted and unplugged the device, and:

Dec  1 21:00:45 khaki kernel: umass0: at uhub0 port 2 (addr 2) disconnected
Dec  1 21:00:45 khaki kernel: (da0:umass-sim0:0:0:0): lost device
Dec  1 21:00:45 khaki kernel: (da0:umass-sim0:0:0:0): removing device entry
Dec  1 21:00:45 khaki kernel: umass0: detached

No sign of any errors anywhere :)

Rowdy