[Bug 252225] won't accept flash drive: "got CAM status 0x50" for Kingston DataTraveler G3

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252225

            Bug ID: 252225
           Summary: won't accept flash drive: "got CAM status 0x50" for
                    Kingston DataTraveler G3
           Product: Base System
           Version: 12.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: corvid at openmailbox.org

Dec 28 03:56:07 <kern.crit> c kernel: ugen0.2: <Kingston DataTraveler G3> at
usbus0
Dec 28 03:56:07 <kern.crit> c kernel: umass0 on uhub0
Dec 28 03:56:07 <kern.crit> c kernel: umass0: <Kingston DataTraveler G3, class
0/0, rev 2.00/1.00, addr 8> on usbus0
Dec 28 03:56:07 <kern.crit> c kernel: umass0:  SCSI over Bulk-Only; quirks =
0xc000
Dec 28 03:56:07 <kern.crit> c kernel: umass0:5:0: Attached to scbus5
Dec 28 03:56:07 <kern.crit> c kernel: GEOM: new disk da0
Dec 28 03:56:07 <kern.crit> c kernel: pass4 at umass-sim0 bus 0 scbus5 target 0
lun 0
Dec 28 03:56:07 <kern.crit> c kernel: pass4: <Kingston DataTraveler G3 1.00>
Removable Direct Access SCSI-2 device
Dec 28 03:56:07 <kern.crit> c kernel: pass4: Serial Number
001CC0EC348DC060C5E4076F
Dec 28 03:56:07 <kern.crit> c kernel: pass4: 40.000MB/s transfers
Dec 28 03:56:07 <kern.crit> c kernel: (da0:umass-sim0:0:0:0): got CAM status
0x50
Dec 28 03:56:07 <kern.crit> c kernel: (da0:umass-sim0:0:0:0): fatal error,
failed to attach to device
Dec 28 03:56:07 <kern.crit> c kernel: da0: Delete methods: <NONE(*),ZERO>
Dec 28 03:56:07 <kern.crit> c kernel: Opened disk da0 -> 6
Dec 28 03:56:07 <kern.crit> c kernel: g_access(961): provider da0 has error 6
set


ugen0.2: <Kingston DataTraveler G3> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=ON (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0930
  idProduct = 0x6544
  bcdDevice = 0x0100
  iManufacturer = 0x0001  <Kingston>
  iProduct = 0x0002  <DataTraveler G3 >
  iSerialNumber = 0x0003  <001CC0EC348DC060C5E4076F>
  bNumConfigurations = 0x0001

 Configuration index 0

    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x0020
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0080
    bMaxPower = 0x0032

    Interface 0
      bLength = 0x0009
      bDescriptorType = 0x0004
      bInterfaceNumber = 0x0000
      bAlternateSetting = 0x0000
      bNumEndpoints = 0x0002
      bInterfaceClass = 0x0008  <Mass storage>
      bInterfaceSubClass = 0x0006
      bInterfaceProtocol = 0x0050
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081  <IN>
        bmAttributes = 0x0002  <BULK>
        wMaxPacketSize = 0x0200
        bInterval = 0x00ff
        bRefresh = 0x0000
        bSynchAddress = 0x0000

     Endpoint 1
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0002  <OUT>
        bmAttributes = 0x0002  <BULK>
        wMaxPacketSize = 0x0200
        bInterval = 0x00ff
        bRefresh = 0x0000
        bSynchAddress = 0x0000

I found in sys/cam/scsi/scsi_da.c that there's a da_quirk_table that already
has a 

        {
                {T_DIRECT, SIP_MEDIA_REMOVABLE, "Kingston", "DataTraveler G3",
                 "1.00"}, /*quirks*/ DA_Q_NO_PREVENT
        },
but I suppose just because two objects say DataTraveler G3 1.00 doesn't mean
they aren't different inside.

-- 
You are receiving this mail because:
You are the assignee for the bug.