From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209555] dwc2 driver stops working after sudden disconnect
Date: Fri, 03 Dec 2021 01:47:34 +0000 [thread overview]
Message-ID: <bug-209555-208809-1qr5HGsTlI@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 #30 from remyvarma@gmail.com ---
I see this:
[ 8.469658] dwc2 ff580000.usb: Core Release: 3.10a (snpsid=4f54310a)
[ 8.482710] dwc2 ff580000.usb: dwc2_core_reset()
[ 8.488584] dwc2 ff580000.usb: Forcing mode to device
[ 8.502210] dwc2 ff580000.usb: Waiting for device mode
[ 8.507962] dwc2 ff580000.usb: Device mode set
[ 8.512932] dwc2 ff580000.usb: Forcing mode to device
[ 8.518577] dwc2 ff580000.usb: Waiting for device mode
[ 8.518584] dwc2 ff580000.usb: Device mode set
[ 8.518611] dwc2 ff580000.usb: NonPeriodic TXFIFO size: 16
[ 8.518615] dwc2 ff580000.usb: RXFIFO size: 275
[ 8.546968] dwc2 ff580000.usb: EPs: 10, dedicated fifos, 972 entries in
SPRAM
[ 8.557497] dwc2 ff580000.usb: DCFG=0x08100000, DCTL=0x00000002,
DIEPMSK=00000000
[ 8.569534] dwc2 ff580000.usb: GAHBCFG=0x00000000, GHWCFG1=0x00006664
[ 8.576754] dwc2 ff580000.usb: GRXFSIZ=0x00000400, GNPTXFSIZ=0x00100400
[ 8.584152] dwc2 ff580000.usb: DPTx[1] FSize=256, StAddr=0x00000410
[ 8.589476] systemd[1]: Started Journal Service.
[ 8.591155] dwc2 ff580000.usb: DPTx[2] FSize=256, StAddr=0x00000900
[ 8.603313] dwc2 ff580000.usb: DPTx[3] FSize=256, StAddr=0x00000a00
[ 8.610314] dwc2 ff580000.usb: DPTx[4] FSize=256, StAddr=0x00000b00
[ 8.617312] dwc2 ff580000.usb: DPTx[5] FSize=256, StAddr=0x00000c00
[ 8.624311] dwc2 ff580000.usb: DPTx[6] FSize=256, StAddr=0x00000d00
[ 8.636845] dwc2 ff580000.usb: DPTx[7] FSize=0, StAddr=0x00000e00
[ 8.643840] dwc2 ff580000.usb: DPTx[8] FSize=0, StAddr=0x00000f00
[ 8.650652] dwc2 ff580000.usb: DPTx[9] FSize=256, StAddr=0x00000410
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-12-03 1:47 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 ` [Bug 209555] " bugzilla-daemon
2020-10-08 7:46 ` 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 [this message]
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-1qr5HGsTlI@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).