All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209555] New: dwc2 driver stops working after sudden disconnect
Date: Tue, 06 Oct 2020 21:59:51 +0000	[thread overview]
Message-ID: <bug-209555-208809@https.bugzilla.kernel.org/> (raw)

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@kernel-bugs.kernel.org
          Reporter: tomasz@grobelny.net
        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.

             reply	other threads:[~2020-10-06 21:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 21:59 bugzilla-daemon [this message]
2020-10-07 20:00 ` [Bug 209555] dwc2 driver stops working after sudden disconnect 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.