On 8/25/2016 12:45 AM, Felipe Balbi wrote: > > Hi, > > Felipe Balbi <felipe.balbi@xxxxxxxxxxxxxxx> writes: >>> On your testing/next, I see considerable slow down and file >>> corruption in mass storage. >>> >>> After bisecting, this patch seems to be the first one that shows >>> problems. The device fails even enumeration here. >>> >>> I haven't looked in detail at the changes but, do you have any ideas? >>> >>> I have attached driver logs. >> >> g_mass_storage doesn't use sglists, so I find this to be unlikely. I'll >> test again but I didn't notice any problems on my side. > > Few things: > > Host sent you a few Resets which I don't know why they're there: > > irq/16-dwc3-2849 [002] d..2 45.257835: dwc3_event: event (00000101): Reset [U0] > > [...] > > irq/16-dwc3-2849 [002] d..2 45.352847: dwc3_event: event (00000101): Reset [U0] > > [...] > > irq/16-dwc3-2849 [002] d..2 45.257835: dwc3_event: event (00000101): Reset [U0] > > [...] > > 4 requests per endpoint, why so few? To test throughput, I've been using > 96 requests per endpoint :-p Any trick to get it to do that? We haven't really used the g_mass_storage for performance testing yet. Regards, John -- 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
