On Thu, Aug 24, 2017 at 02:05:22PM +0200, Massimo Burcheri wrote: > Hello, > > as reported on > https://bugzilla.kernel.org/show_bug.cgi?id=196739 > > a Transcend 25M3 device with ASM1153 chipset is detected as ASM1051 and breaking > UAS support as this one is blacklisted. But after contacting the manufacturer > claimed this model has a ASM1153 and supported by UASP. So I double checked the > chip on the microscope and it is true, this is a ASM1153 and detection has > failed. > > syslog after attaching: > > [kernel] usb 4-2: new SuperSpeed USB device number 4 using xhci_hcd > [kernel] usb 4-2: New USB device found, idVendor=174c, idProduct=5106 > [kernel] usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 > [kernel] usb 4-2: Product: StoreJet Transcend > [kernel] usb 4-2: Manufacturer: StoreJet Transcend > [kernel] usb 4-2: SerialNumber: S36VJ9CH307FOO > [kernel] usb-storage 4-2:1.0: USB Mass Storage device detected > [kernel] scsi host7: usb-storage 4-2:1.0 > [kernel] scsi 7:0:0:0: Direct-Access StoreJet Transcend 0 PQ: 0 ANSI: 6 > [kernel] sd 7:0:0:0: Attached scsi generic sg3 type 0 > [kernel] sd 7:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) > [kernel] sd 7:0:0:0: [sdd] Write Protect is off > [kernel] sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > [kernel] sdd: sdd1 > [kernel] sd 7:0:0:0: [sdd] Attached SCSI disk > > From lsusb -vv: > > Bus 004 Device 005: ID 174c:5106 ASMedia Technology Inc. ASM1051 SATA 3Gb/s bridge > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 3.00 > bDeviceClass 0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 9 > idVendor 0x174c ASMedia Technology Inc. > idProduct 0x5106 ASM1051 SATA 3Gb/s bridge The product id matches that of the ASM1051, so why would the kernel ignore what the firmware told it? What is the product id that you think this device should be reporting instead? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
