https://bugzilla.kernel.org/show_bug.cgi?id=209555 Bug ID: 209555 Summary: dwc2 driver stops working after sudden disconnect Product: Drivers Version: 2.5 Kernel Version: 5.9.0-rc6 Hardware: ARM OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: USB Assignee: drivers_usb@xxxxxxxxxxxxxxxxxxxxxx Reporter: tomasz@xxxxxxxxxxxx Regression: No Created attachment 292875 --> https://bugzilla.kernel.org/attachment.cgi?id=292875&action=edit dmesg Setup: # uname -a Linux odroid 5.9.0-rc6-dirty #1 SMP PREEMPT Tue Oct 6 20:04:44 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux dwc2 driver working in gadget mode on Odroid N2 using function fs kernel: branch next from git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git Scenario: Odroid connects as custom gadget (with mass storage function, see second 114 and 134), then is switched to Android Open Accessory mode and start transmission using function fs (uses ep0,ep1,ep2 channels). Suddenly the USB cable is pulled out (roughly second 122). Running the same sequence of actions (second 134) does not work any more until reboot. In dmesg one can see timeouts. Also, before enabling debug output I could see "HANG! Soft Reset timeout GRSTCTL_CSFTRST_DONE" line in dmesg output (drivers/usb/dwc2/core.c:538) Therefore my conclusion is that there is something wrong with handling device disconnect. Due to number of produced debug messages dmesg output might be incomplete. Please let me know if I can somehow help to fix this bug. -- You are receiving this mail because: You are watching the assignee of the bug.
