All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212725] New: USB CDC ACM device stop working
Date: Mon, 19 Apr 2021 21:18:02 +0000	[thread overview]
Message-ID: <bug-212725-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=212725

            Bug ID: 212725
           Summary: USB CDC ACM device stop working
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.11.15
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: stefan@agner.ch
        Regression: No

When trying to use USB CDC ACM devices (open using screen) opening fails and
the kernel dmesg shows the following error:

kernel: cdc_acm 1-3.3.3:1.0: acm_port_activate - usb_submit_urb(ctrl irq)
failed

This happens with STM32 microcontroller based device as well as a Segger JTAG
adapter, so it seems not device related. The issue must have been introduced
recently (within the last month) as those devices used to work previously. I
can reproduce the issue also with latest LTS kernel release 5.10.31.

Builds:
- 5.10.31-1-lts
- 5.11.15-arch1-2

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-04-19 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 21:18 bugzilla-daemon [this message]
2021-04-19 21:26 ` [Bug 212725] USB CDC ACM device stop working bugzilla-daemon
2021-04-19 21:34 ` bugzilla-daemon
2021-04-20  9:58 ` bugzilla-daemon
2021-04-20 13:35 ` bugzilla-daemon
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@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.