Re: ASMedia AS2105 interface on USB 3.0 corrupts data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05.06.2014, Mathias Nyman wrote: 

> What kind of a hard drive did you have connected? 
> and with what filsystem? Just in case if that somehow affects the USB traffic.

The HDD is a Western Digital 160 GB drive, here's the (abridged) output of
"hdparm -I" 

[root@keera ~]# hdparm -I /dev/sdc

/dev/sdc:

ATA device, with non-removable media
    Model Number:       WDC WD1600BEVS-08RST2                   
    Serial Number:      WD-WXC608K43031
    Firmware Revision:  08.01G08
Standards:
	Supported: 7 6 5 4 
	Likely used: 8
Configuration:
	Logical		max	current
	cylinders	16383	16383
	heads			16	16
	sectors/track		63	63
	--
	CHS current addressable sectors:   16514064
	LBA    user addressable sectors:  268435455
	LBA48  user addressable sectors:  312581808
	Logical/Physical Sector size:           512 bytes
	device size with M = 1024*1024:      152627 MBytes
	device size with M = 1000*1000:      160041 MBytes (160 GB)
	cache/buffer size  = 8192 KBytes

The filesystem I use exclusively is XFS. But I wrote directly to the device itself:
dd if=/dev/zero of=/dev/sdb bs=8M 

DD starts to write, and after some 4-5 GB writing, the drive
disconnects. This is what dmesg shows:

First there are a whole lot (really a lot!) of these lines:
[ 308.778543] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802205ef6c0
[ 309.139556] usb 9-1: reset SuperSpeed USB device number 3 using xhci_hcd
[  309.152263] usb 9-1: Parent hub missing LPM exit latency info. Power management will be impacted.
[  309.153511] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802205ef680
[  309.153525] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802205ef6c0

And then, after dd'ing some GB, this happens:
[  309.936299] usb 9-1: device not accepting address 3, error -22
[  310.691924] usb 9-1: device not accepting address 3, error -22
[  311.447552] usb 9-1: device not accepting address 3, error -22
[  312.203177] usb 9-1: device not accepting address 3, error -22
[  312.203499] usb 9-1: USB disconnect, device number 3
[  312.209225] sd 9:0:0:0: [sdb] Unhandled error code
[  312.209230] sd 9:0:0:0: [sdb]  
[  312.209232] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  312.209234] sd 9:0:0:0: [sdb] CDB: 
[  312.209235] Write(10): 2a 00 00 65 9c d0 00 00 f0 00
[  312.209240] end_request: I/O error, dev sdb, sector 6659280
[  312.209243] Buffer I/O error on device sdb, logical block 832410
[  312.209243] lost page write due to I/O error on sdb
[  312.209247] Buffer I/O error on device sdb, logical block 832411
[  312.209248] lost page write due to I/O error on sdb
[  312.209250] Buffer I/O error on device sdb, logical block 832412
[  312.209250] lost page write due to I/O error on sdb
[  312.209252] Buffer I/O error on device sdb, logical block 832413
[  312.209253] lost page write due to I/O error on sdb
[  312.209254] Buffer I/O error on device sdb, logical block 832414
[  312.209254] lost page write due to I/O error on sdb
[  312.209256] Buffer I/O error on device sdb, logical block 832415
[  312.209256] lost page write due to I/O error on sdb
[  312.209258] Buffer I/O error on device sdb, logical block 832416
[  312.209259] lost page write due to I/O error on sdb
[  312.209260] Buffer I/O error on device sdb, logical block 832417
[  312.209261] lost page write due to I/O error on sdb
[  312.209262] Buffer I/O error on device sdb, logical block 832418
[  312.209263] lost page write due to I/O error on sdb
[  312.209264] Buffer I/O error on device sdb, logical block 832419
[  312.209265] lost page write due to I/O error on sdb
[  312.210892] sd 9:0:0:0: [sdb] Unhandled error code
[  312.210898] sd 9:0:0:0: [sdb]  
[  312.210903] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  312.210909] sd 9:0:0:0: [sdb] CDB: 
[  312.210912] Write(10): 2a 00 00 65 9d c0 00 00 f0 00
[  312.210916] end_request: I/O error, dev sdb, sector 6659520
[  312.991819] sd 9:0:0:0: [sdb] Synchronizing SCSI cache
[  312.991855] sd 9:0:0:0: [sdb]  
[  312.991857] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  312.991979] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called  with disabled ep ffff8802205ef680
[  312.991981] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802205ef6c0

I guess the buffer I/O errors occur because the device has already
disconnected? (just guessing, I really don't know).

And here, the device which has been /dev/sdb re-connects, automatically, and gets assigned
to /dev/sdc (while dd continues trying to write to /dev/sdb, which now is /dev/sdc):

[  313.198499] usb 9-1: new SuperSpeed USB device number 4 using xhci_hcd
[  313.211292] usb 9-1: Parent hub missing LPM exit latency info. Power management will be impacted.
[  313.214982] usb 9-1: New USB device found, idVendor=174c, idProduct=5136
[  313.214991] usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  313.214997] usb 9-1: Product: AS2105
[  313.215003] usb 9-1: Manufacturer: ASMedia
[  313.215008] usb 9-1: SerialNumber: 00000000000000000000
[  313.216941] usb-storage 9-1:1.0: USB Mass Storage device detected
[  313.217786] scsi10 : usb-storage 9-1:1.0
[  314.220208] scsi 10:0:0:0: Direct-Access     ASMT     2105 0    PQ: 0 ANSI: 6
[  314.221007] sd 10:0:0:0: Attached scsi generic sg2 type 0
[  314.223137] sd 10:0:0:0: [sdc] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[  314.227139] sd 10:0:0:0: [sdc] Write Protect is off
[  314.227151] sd 10:0:0:0: [sdc] Mode Sense: 43 00 00 00
[  314.228361] sd 10:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  314.283054] sdc: unknown partition table
[  314.285983] sd 10:0:0:0: [sdc] Attached SCSI disk

This is the USB-3 controller used in this case:
02:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)

When I connect this controller/drive to USB-2, it works flawlessly.
The same happens using a WD 500 GB "black" HDD. Both harddrives are
100% ok. Reformatted, they work flawlessly on any USB-2 port of the
same machine.

The same (faulty) behaviour also occurs on a HP laptop (USB-3) booted
from an external medium into sysresccd (Gentoo).

I have not the slightest clue what's going on here..

Thanks,
 Heinz.
--
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




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux