Bug 192375 - Kingston DataTraveler G2 memory stick doesn't work
Summary: Kingston DataTraveler G2 memory stick doesn't work
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 9.3-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-04 10:28 UTC by gja822
Modified: 2022-01-16 13:20 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gja822 2014-08-04 10:28:50 UTC
I've got this when inserting this very usb memory stick. And, no /dev/da* devices created. More over, when I de-inserting stick, I've got problems, such as when I de-insert with mounted stick (PS/2 keyboard dies!, other bug report?).


ugen7.2: <Kingston> at usbus7
umass0: <Kingston DataTraveler G2, class 0/0, rev 2.00/1.00, addr 2> on usbus7
umass0:  SCSI over Bulk-Only; quirks = 0x0100
umass0:11:0:-1: Attached to scbus11
da0 at umass-sim0 bus 0 scbus11 target 0 lun 0
da0: <Kingston DataTraveler G2 1.00> Removable Direct Access SCSI-2 device 
da0: Serial Number 001CC0EC330FF02026BF0D49
da0: 40.000MB/s transfers
da0: 7634MB (15636304 512 byte sectors: 255H 63S/T 973C)
da0: quirks=0x2<NO_6_BYTE>
(da0:umass-sim0:0:0:0): got CAM status 0x50
(da0:umass-sim0:0:0:0): fatal error, failed to attach to device
da0 at umass-sim0 bus 0 scbus11 target 0 lun 0
da0: <Kingston DataTraveler G2 1.00> s/n 001CC0EC330FF02026BF0D49 detached
(da0:umass-sim0:0:0:0): Periph destroyed
Comment 1 gja822 2016-09-18 17:12:03 UTC
Now, on    10.3-STABLE amd64   it kills part of USB subsystem on detaching this Kingston flash stick, leaving working USB mouse, but no chance to use USB flash sticks before reboot. And in /dev/da* it leave the device.
'usbconfig list' command just hangs forever (hopefully could be Ctrl+C'd) after detaching. (I do unmount it and I can mount and transfer data to/from it for the first time it attached).
Comment 2 Peter Much 2021-12-29 14:39:30 UTC
I have the same piece:

ugen0.2: <Kingston DataTraveler G2> at usbus0
umass0 numa-domain 0 on uhub0
umass0: <Kingston DataTraveler G2, class 0/0, rev 2.00/1.00, addr 1> on usbus0
umass0:  SCSI over Bulk-Only; quirks = 0xc100
umass0:14:0: Attached to scbus14
da7 at umass-sim0 bus 0 scbus14 target 0 lun 0
da7: <Kingston DataTraveler G2 1.00> Removable Direct Access SCSI-2 device
da7: Serial Number ************************
da7: 40.000MB/s transfers
da7: 15269MB (31272544 512 byte sectors)
da7: quirks=0x6<NO_6_BYTE,NO_PREVENT>

As you can see, I added the NO_PREVENT quirk to make it work. Works fine now.

In sys/cam/scsi/scsi_da.c we already have this for the G3 version. I simply
expanded that to also handle the G2.

        {
-               {T_DIRECT, SIP_MEDIA_REMOVABLE, "Kingston", "DataTraveler G3",
+               {T_DIRECT, SIP_MEDIA_REMOVABLE, "Kingston", "DataTraveler G*",
                 "1.00"}, /*quirks*/ DA_Q_NO_PREVENT
        },
Comment 3 gja822 2022-01-15 18:01:30 UTC
(In reply to Peter Much from comment #2)
Well, now on FreeBSD (12.3-STABLE r371482) the flash stick works. I've made no hand intrusion in the source.

ugen6.2: <Kingston DataTraveler G2> at usbus6
umass0 on uhub7
umass0: <Kingston DataTraveler G2, class 0/0, rev 2.00/1.00, addr 2> on usbus6
umass0:  SCSI over Bulk-Only; quirks = 0xc100
umass0:8:0: Attached to scbus8
da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
da0: <Kingston DataTraveler G2 1.00> Removable Direct Access SCSI-2 device
da0: Serial Number 001CC0EC330FF02026BF0D49
da0: 40.000MB/s transfers
da0: 7634MB (15636304 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>

(And you have a bit different device, yours is 16Gb, mine is 8Gb).
Comment 4 Tomasz "CeDeROM" CEDRO 2022-01-16 13:20:38 UTC
128GB also works on 13.0-RELEASE. Although I noticed that it only works when directly connected to USB port, I had problems when attaching over USB 3.0 HUB, disk was detected in dmesg then /dev/da0 was not showing up, but that problem seems to be fixed on 13-STABLE now, so it should also show up in the release soon, thank you! :-)