On 01/12/2018 01:01 PM, Felipe Balbi wrote: >>>> This fixed random occasional failures that were previously observed on a >>>> DWC3 based system under high system load. >>> >>> I need to see tracepoint capture from the failure ;-) Care to send them >>> to me for analysis? >> >> I've attached the full trace up to the point where the failure occurs. (The >> tracing infrastructure in the DWC3 driver was very helpful in tracking this >> down btw.). > > yeah, that was the idea. I see, however, that you're using an older > kernel based on the your trace format. Just to make sure, did you try > with v4.14? I see the problem is pretty clear and we will take the > patch, but just to make sure, can you try v4.14? > I wish I could. The only SoC I have with DWC3 isn't fully supported in upstream yet and the vendor kernel is still at v4.9. I've tried it with other UDC drivers running v4.14 just to make sure there is no regression. Do you have a system with DWC3 that you can run in gadget mode? If you use the aio_simple.c from the function fs examples and put a sleep(1) (or something similar) in handle_ep0() after the display_event(&event) that should emulate the scheduling due to high system load and should be able to reproduce the issue when the patch is not applied. -- 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
