Martin Mokrejs wrote: > Martin Mokrejs wrote: >> >> >> Martin Mokrejs wrote: >>> Hi, >>> I just bought a Silverstone Treasure TS04B external case. I thought >>> it will be based on ASMedia1051 chip but maybe because of the 'B' at >>> the end ... ? >>> >>> When I read from a SATAII disk placed into the casing I read at about >>> 32MB/s (from raw disk -- dd if=/dev/sdc of=/dev/null) when having connected >>> it to either internal Texas Instruments USB3.0 chip or to a NEC USB3.0 chip >>> in an Express Card. I conclude this is not an issue with the host controller >>> chipset in my laptop Dell Vostro 3550 or the Express card but an issue with >>> xhci_hcd or the ASMedia2105 chip. That was with 3.3.4 kernel. >>> >>> I found something on the internet reported by people having an onboard >>> ASMedia controller which can be switched by BIOS from XHCI to EHCI .. >>> I do not understand whether that relates to me or not. Aside from the fact >>> that I have the ASMedia chip in the "client" device (a HDD enclosure). >>> >>> If I look into the "lsusb -t" output I see the device is at 480Mbps. >>> Why? I rebooted into 3.4-rc5 and first, connected the enclosure to the >>> TexasInstruments USB3 port. >>> >>> This gave me: >>> >>> [ 92.996770] usb 3-2: new high-speed USB device number 2 using xhci_hcd >>> [ 93.056517] xhci_hcd 0000:0b:00.0: device LPM test failed, may disconnect and re-enumerate >>> [ 93.064234] usb 3-2: New USB device found, idVendor=174c, idProduct=5106 >>> [ 93.064245] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 >>> [ 93.064252] usb 3-2: Product: AS2105 >>> [ 93.064257] usb 3-2: Manufacturer: ASMedia >>> [ 93.064262] usb 3-2: SerialNumber: WD-WX51C10U8155 >>> [ 93.064436] usb 3-2: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes >>> [ 93.064443] usb 3-2: ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes >>> [ 93.065037] scsi7 : usb-storage 3-2:1.0 >>> >>> but I wasn't catching the USB trafiic, so you only see in the attached dmesg output. >>> On next two re-plkugs of the device it did not happen. >>> >>> >>> Then I unpugged it, started usbmon to catch traffic on the same port (the >>> port remained in the 480Mbps mode, claimed by xhci_hcd). I ran smartctl to fetch >>> some SMART data from the disc and unplugged it again. The recorded file is named >>> 3.4-rc5-ASMedia2105_via_Texas_instruments_Bus3_reporting_480Mbps.usbmon.out >>> and logs are in 3.4-rc5-ASMedia2105_via_Texas_instruments_Bus3_reporting_480Mbps.txt. >>> >>> >>> >>> Then, I saw the other port coming out from the Texas Instruments chip is >>> still in 5Gbps mode, so I started to record USB traffic again, connected the >>> enclosure to that port and likewise, it is in 3.4-rc5-ASMedia2105_via_Texas_instruments_Bus4_reporting_5Gbps.usbmon.out >>> and logs in 3.4-rc5-ASMedia2105_via_Texas_instruments_Bus4_reporting_5Gbps.txt. >>> >>> I hope you can infer something from them as I will probably return the external >>> enclosure and go for the "old" ASMedia1051 in Silvertsone RVS02 (if I am lucky >>> to grab the right piece). >>> >>> Whats of interest in the ASMedia2005 chip, btw? >>> >>> (I can repeat the test with NEC Corporation uPD720200 USB 3.0 if you want). >> >> So when connected to the NEC controller I found out 'uas' driver is being used: >> http://pastebin.com/E89fESQ0 . And with UAS driver omitted from the kernel I get: >> http://pastebin.com/pAdmuhpM (merely same - only at high-speeed). >> >> The race between suspend and wekeup sounds weird (a snippet from the latter pastebin): > >> When I removed also the USB power management although the race messages obviously disappeared >> but I still get only high-speed connection: http://pastebin.com/dzSbyPGM . > > Finally, one more. The disk attached to ASMedia2105 dies itself: > ASMedia2105-bridge-connects-only-as-high-speed__no_UAS_no_USB_PowerManagement_in_kernel__disk_dies_itself.txt > > I see same bad behavior in Windows 7, that is when connected via the NEC chip the > ASMedia2105 device is recognized only at high-speed. When I try to access the disk > it resets and makes ugly click like heads hitting the media in the drive. :( > The same sound I hear but repeatedly every few seconds if the disk is powered on but > not attached to upstream USB controller. > > The device disconnects I do not have when the ASMedia2105 is connected to a Texas > Instruments USB3 controller in Windows 7. But, it also negotiates at high-speed only, > and HD Tach timings show transfers about 32MB/s confirming that. > > Finally, I opened the box casing and looked at the chip. It is actually ASMedia1051 > (ASM1051 A4P05920A1 T6A 1050) and based on http://www.hardwareluxx.de/community/f15/2-5-hdd-gehaeuse-usb-3-0-mit-smart-wert-ubertragung-gesucht-805955-2.html > it is the revision A2 but it doesn't seem so. Nevertheless, it itself reports via USB ---------------------^^ should be A1 and that is what is printed on the chip itself > as ASM2105, same info received Linux host and same on Windows 7. A firmware upgrading > utility for ASM1051 from http://www.station-drivers.com/page/asmedia.htm exits because > it is a wrong chip, probably because a dumped backup image file has different size. > > At least I can confirm that when attached to USB2 controller (or Texas Instruments USB3 > under Linux) it works fine and S.M.A.R.T. is reported from the inserted disk (WD10TPVT), > even temperature readings. > > This device goes out of my door now. > > Maybe all these test will be useful to somebody else in future. I think I know why it gets detected only at high-speed. The Silverstone RVS02 has working ASM1051 (likely rev. A0) in USB3 mode. The Treasure TS04B has ASM1051 rev. A1 (aka ASM2105): # diff -u -w RVS02.txt TS04B.txt --- RVS02.txt 2012-05-03 11:56:15.000000000 +0200 +++ TS04B.txt 2012-05-03 11:55:50.000000000 +0200 @@ -1,23 +1,23 @@ -Bus 004 Device 002: ID 174c:55aa ASMedia Technology Inc. +Bus 003 Device 003: ID 174c:5106 ASMedia Technology Inc. Device Descriptor: bLength 18 bDescriptorType 1 - bcdUSB 3.00 + bcdUSB 2.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 - bMaxPacketSize0 9 + bMaxPacketSize0 64 idVendor 0x174c ASMedia Technology Inc. - idProduct 0x55aa - bcdDevice 1.00 - iManufacturer 2 SST - iProduct 3 RVS02 SuperSpeed - iSerial 1 0000000000000000FE + idProduct 0x5106 + bcdDevice 0.01 + iManufacturer 2 ASMedia + iProduct 3 AS2105 + iSerial 1 WD-WX51C10U8155 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 - wTotalLength 44 + wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 @@ -42,9 +42,8 @@ Transfer Type Bulk Synch Type None Usage Type Data - wMaxPacketSize 0x0400 1x 1024 bytes + wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 - bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 @@ -53,33 +52,8 @@ Transfer Type Bulk Synch Type None Usage Type Data - wMaxPacketSize 0x0400 1x 1024 bytes + wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 - bMaxBurst 15 -Binary Object Store Descriptor: - bLength 5 - bDescriptorType 15 - wTotalLength 22 - bNumDeviceCaps 2 - USB 2.0 Extension Device Capability: - bLength 7 - bDescriptorType 16 - bDevCapabilityType 2 - bmAttributes 0x00000002 - Link Power Management (LPM) Supported - SuperSpeed USB Device Capability: - bLength 10 - bDescriptorType 16 - bDevCapabilityType 3 - bmAttributes 0x00 - Latency Tolerance Messages (LTM) Supported - wSpeedsSupported 0x000e - Device can operate at Full Speed (12Mbps) - Device can operate at High Speed (480Mbps) - Device can operate at SuperSpeed (5Gbps) - bFunctionalitySupport 1 - Lowest fully-functional device speed is Full Speed (12Mbps) - bU1DevExitLat 10 micro seconds - bU2DevExitLat 2047 micro seconds Device Status: 0x0001 Self Powered + Martin -- 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
