At 12:17 PM 11/22/2011 -0800, Sarah Sharp wrote: >On Mon, Nov 14, 2011 at 04:51:43PM -0500, starlight@xxxxxxxxxxx wrote: >> >> I'm experiencing a write-test failure with >> a WDC MyBook 3TB. ... >> >> Briefly >> >> # dd bs=1024k if=/dev/zero of=test oflag=direct >> dd: writing `test': Read-only file system >> 10017+0 records in >> 10016+0 records out >> 10502537216 bytes (11 GB) copied, 132.675 s, 79.2 MB/s >> . . . >A patch was sent out last week for the 3.2 kernel >that fixes an issue with the AsMedia host >controller: > >d31c285 xhci: Set slot and ep0 flags for address >command. > >It's marked for the stable kernel, so it should >make it into 3.1 soon. > >It's possible that the problem lies with the >combination of your AsMedia host controller and >the device, not with the device alone. The patch >that went in fixes a case where the xHCI driver >feels the host controller bad data, but only if >the device needs a reset (which some storage >devices do when they decide they can't handle a >particular SCSI command). So the MyBook might >trigger the xHCI driver bug, but your new drive >appears not to. > >Any chance you can try the latest kernel from >Linus' tree and see if it fixes your problem? Tried the problem drive with the 3.2.0-rc2 kernel and the 'dd' write test and it appears to work fine. Let it run for only 50GB, so it wasn't an exhaustive test. Also tried it with 3.1.1 and it worked there as well, so it appears that whatever was causing the MyBook to fail with the RH 6.0 kernel was fixed before the recent patches. This implies that specific issue that the Gentoo forum user experienced is different than the one seen here since his test failed with 3.1.1, even though the 'dmesg' output was nearly identical. That was a Mukii drive enclosure with a JMS539 USB3/SATA bridge controller (the MyBook has a Symwave SW6316). I'm posting to that thread in case he is interested it testing latest USB3 patches found in 3.2.0-rc2. -- 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
