From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209555] dwc2 driver stops working after sudden disconnect
Date: Wed, 07 Oct 2020 20:00:22 +0000 [thread overview]
Message-ID: <bug-209555-208809-00s8GYVO5Z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209555-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209555
--- Comment #1 from Tomasz Grobelny (tomasz@grobelny.net) ---
Here is annotated dmesg without debugging info:
[ 31.709214] USB_PWR_EN: disabling
//here I connect the cable and run my program
[ 54.771552] Mass Storage Function, version: 2009/09/11
[ 54.771561] LUN: removable file: (no medium)
[ 54.781721] file system registered
[ 54.782484] read descriptors
[ 54.782495] read strings
[ 54.786939] dwc2 ff400000.usb: bound driver configfs-gadget
[ 54.976434] dwc2 ff400000.usb: new device is high-speed
[ 55.090994] dwc2 ff400000.usb: new device is high-speed
[ 55.142436] dwc2 ff400000.usb: new address 4
[ 56.219325] ffs_data_put(): freeing
[ 56.219828] unloading
//here the switch to AOA mode happens: it is as if the device was disconected
and entirely new device (different vid, pid) connected
[ 56.257710] file system registered
[ 56.258362] read descriptors
[ 56.258373] read strings
[ 56.262135] dwc2 ff400000.usb: bound driver configfs-gadget
[ 56.454364] dwc2 ff400000.usb: new device is high-speed
[ 56.568367] dwc2 ff400000.usb: new device is high-speed
[ 56.620390] dwc2 ff400000.usb: new address 5
// here the cable is disconnected
[ 79.288505] dwc2 ff400000.usb: dwc2_hsotg_ep_stop_xfr: timeout
DIEPINT.NAKEFF
[ 79.288625] dwc2 ff400000.usb: dwc2_hsotg_ep_stop_xfr: timeout
DOEPCTL.EPDisable
[ 79.299850] dwc2 ff400000.usb: dwc2_flush_tx_fifo: HANG! AHB Idle GRSCTL
[ 79.299982] dwc2 ff400000.usb: dwc2_hsotg_ep_stop_xfr: timeout
GINTSTS.GOUTNAKEFF
[ 79.300105] dwc2 ff400000.usb: dwc2_hsotg_ep_stop_xfr: timeout
DOEPCTL.EPDisable
[ 79.307060] ffs_data_put(): freeing
[ 79.307355] unloading
// rmmod dwc2 && modprobe dwc2
[ 119.388282] dwc2 ff400000.usb: supply vusb_d not found, using dummy
regulator
[ 119.388349] dwc2 ff400000.usb: supply vusb_a not found, using dummy
regulator
[ 119.388500] dwc2 ff400000.usb: Bad value for GSNPSID: 0x00000000
// run my program again, as you see it doesn't reach the "bound driver
configfs-gadget" line seen above
[ 255.814129] Mass Storage Function, version: 2009/09/11
[ 255.814138] LUN: removable file: (no medium)
[ 255.814545] file system registered
[ 255.815119] read descriptors
[ 255.815128] read strings
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-10-07 20:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 21:59 [Bug 209555] New: dwc2 driver stops working after sudden disconnect bugzilla-daemon
2020-10-07 20:00 ` bugzilla-daemon [this message]
2020-10-08 7:46 ` [Bug 209555] " bugzilla-daemon
2020-10-08 19:47 ` bugzilla-daemon
2020-10-09 6:47 ` bugzilla-daemon
2021-02-26 1:43 ` bugzilla-daemon
2021-07-24 16:42 ` bugzilla-daemon
2021-07-25 5:45 ` Minas Harutyunyan
2021-07-25 5:45 ` bugzilla-daemon
2021-07-25 6:55 ` bugzilla-daemon
2021-07-25 7:16 ` Minas Harutyunyan
2021-07-25 7:23 ` Minas Harutyunyan
2021-07-25 7:17 ` bugzilla-daemon
2021-07-25 7:23 ` bugzilla-daemon
2021-07-25 8:52 ` bugzilla-daemon
2021-07-25 14:25 ` bugzilla-daemon
2021-07-25 15:14 ` bugzilla-daemon
2021-07-26 5:08 ` bugzilla-daemon
2021-12-02 23:42 ` bugzilla-daemon
2021-12-03 0:20 ` bugzilla-daemon
2021-12-03 0:40 ` bugzilla-daemon
2021-12-03 0:43 ` bugzilla-daemon
2021-12-03 0:44 ` bugzilla-daemon
2021-12-03 1:08 ` bugzilla-daemon
2021-12-03 1:47 ` bugzilla-daemon
2021-12-07 2:13 ` bugzilla-daemon
2022-02-19 11:11 ` bugzilla-daemon
2022-02-19 11:11 ` bugzilla-daemon
2022-05-18 10:20 ` bugzilla-daemon
2023-05-03 1:56 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209555-208809-00s8GYVO5Z@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).