On Tue, Apr 13, 2010 at 11:54 PM, Sarah Sharp <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > If your host controller is at fault, it may be necessary for the xHCI > driver to limit the number of sglist entries so your buggy host > controller doesn't crash. Can you experiment with changing this line in > xhci-pci.c: > > hcd->self.sg_tablesize = TRBS_PER_SEGMENT - 1; > > Try leaving TRBS_PER_SEGMENT set to 64, and then modifying this line to > limit the sglist to something small, like 10 or 25. Run the default USB > mass storage driver and see if this resolves the HC died issue for you. > If it does, try to find the maximum size that makes the host not die. Dear Sarah, Thank you very much for the information. Today, I tried with the following scenario with default mass storage driver in 2.6.34-rc2 (xhci-large-tx branch). The TRBS_EPR_SGEMENT is set to 64 and SEGMENT_SHIFT is set to 10 in xhci.h file. Also, I tested with the hcd->self.sg_tablesize by setting it to 10 and 25. Unfortunately, the data transfer failed again. The value of the max_sectors is set to 960 in both the cases. I saw “HW died” in both the cases. However the root cause still remains the same. The host just stops working, after submitting data and remains waiting for an interrupt which doesn’t occur. After a time out, command_abort is called, followed by a print statement which says “HW died” The other thing is, the same host controller is working under Windows for larger transfers without any issues. We have tested the host under Windows up to 2 MB transfer buffers and it works fine without any issues. So, I am doubting that it could be a hardware issue. Also, it seems to work fine with USB2.0 cable. Please let me know if you need any additional information. Thanks and Regards, Ramya. -- 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
