usb/80361: mounting of usb-stick fails

[Fridtjof Busse]

>Number:         80361
>Category:       usb
>Synopsis:       mounting of usb-stick fails
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-usb
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 26 13:10:21 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Fridtjof Busse
>Release:        5.4-RC3
>Organization:
>Environment:
>Description:
If I try to mount my Dell Memory Stick 256 MB, I only get /dev/da0 (and not /dev/da0s1) and this appears in dmesg:

umass0: M-SysT5 Dell Memory Key, rev 2.00/2.00, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <M-SysT5 Dell Memory Key 5.00> Removable Direct Access SCSI-0 device 
da0: 1.000MB/s transfers
da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0
(da0:umass-sim0:0:0:0): Medium not present

The "Medium not present" error is displayed multiple times until it fails with:
(da0:umass-sim0:0:0:0): Retries Exhausted
Opened disk da0 -> 6

The only way to get /dev/da0s1 is to do the following:
cat /dev/null > /dev/da0s1
Then I get da0s1 and everything works fine, filesystem ist FAT32. But I'd like to be able to mount the stick without this "workaround", it works under Linux-2.6 without any problems at all.
The dmesg during the "cat" is:

(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed
(da0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
>How-To-Repeat:
Try to mount a current Dell Memory Stick. There's been a report on questions@ about the same behavior with a Kingston Elite
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted: