From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212725] USB CDC ACM device stop working
Date: Tue, 20 Apr 2021 13:35:53 +0000 [thread overview]
Message-ID: <bug-212725-208809-HwOp6Ez4bf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212725-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212725
--- Comment #4 from Stefan Agner (stefan@agner.ch) ---
Thanks for the quick response!
Applied and built a 5.11.15 kernel with that patch. It indeed seems to fix the
issue!
It did not apply cleanly on 5.11.15 or master, there is a `spin_lock_irq` in
that area. I just moved the acm_unpoison_urbs after the suspend counter
decrement, not sure if that is the correct fix though.
--
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-04-20 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 21:18 [Bug 212725] New: USB CDC ACM device stop working bugzilla-daemon
2021-04-19 21:26 ` [Bug 212725] " bugzilla-daemon
2021-04-19 21:34 ` bugzilla-daemon
2021-04-20 9:58 ` bugzilla-daemon
2021-04-20 13:35 ` bugzilla-daemon [this message]
2021-04-22 11:36 ` bugzilla-daemon
2021-04-28 21:39 ` 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-212725-208809-HwOp6Ez4bf@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).