From: Johan Hovold <johan@kernel.org>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 212751] New: acm_port_activate - usb_submit_urb(ctrl irq) failed after kernel update
Date: Fri, 23 Apr 2021 10:31:54 +0200 [thread overview]
Message-ID: <YIKF+r22o2jKSoxo@hovoldconsulting.com> (raw)
In-Reply-To: <bug-212751-208809@https.bugzilla.kernel.org/>
On Thu, Apr 22, 2021 at 04:32:51PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=212751
>
> Bug ID: 212751
> Summary: acm_port_activate - usb_submit_urb(ctrl irq) failed
> after kernel update
> Product: Drivers
> Version: 2.5
> Kernel Version: 5.10.30
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: USB
> Assignee: drivers_usb@kernel-bugs.kernel.org
> Reporter: johann.wilhelm@wilhelm.consulting
> Regression: No
>
> Something between 5.10.26 and 5.20.30 broke (at least) the USB CDC
> implementation by ST Microsystems on their STM32 devices.
>
> On opending of the device following error occurs:
> [ 1333.790160] cdc_acm 1-10:1.0: acm_port_activate - usb_submit_urb(ctrl irq)
> failed
>
>
> 5.10.26 works - 5.10.30 does not.
This is likely due to commit 6069e3e927c8 ("USB: cdc-acm: untangle a
circular dependency between callback and softint") which had a bug that
was just fixed by commit a8b3b519618f ("USB: CDC-ACM: fix
poison/unpoison imbalance").
You can try applying the latter yourself but it will otherwise show up
in stable soon.
Johan
next prev parent reply other threads:[~2021-04-23 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 16:32 [Bug 212751] New: acm_port_activate - usb_submit_urb(ctrl irq) failed after kernel update bugzilla-daemon
2021-04-23 8:31 ` [Bug 212751] " bugzilla-daemon
2021-04-23 8:31 ` Johan Hovold [this message]
2021-05-27 12:54 ` bugzilla-daemon
2021-06-10 11:09 ` 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=YIKF+r22o2jKSoxo@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=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).