Bug 1950958 - cdc_acm acm_port_activate usb_submit_urb(ctrl irq) failed
Summary: cdc_acm acm_port_activate usb_submit_urb(ctrl irq) failed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-19 09:32 UTC by dzug.koeln-muenchen
Modified: 2022-06-07 22:31 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-07 22:31:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dzug.koeln-muenchen 2021-04-19 09:32:17 UTC
1. Please describe the problem:

If I connect any Arduino Uno (using different cables and USB ports), and then try to use it with the Arduino IDE, or even only do `cat /dev/ttyACM0` (or any other method to open the device), I get errno 5 (EIO). Relevant dmesg line:

```
[   38.520367] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[   48.499829] cdc_acm 1-3:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
```

2. What is the Version-Release number of the kernel:

5.11.11-300
5.11.12-300
5.11.13-300
5.11.14-300

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Haven't tried before 5.11.11 on Fedora, but it works on any 5.11 series kernel on another machine running Manjaro. 

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Connect Arduino Uno to Lenovo Ideapad C340/AMD and try to open its port (IDE, cat or python script).

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Problem: 5.12.0-0.rc7 kernel packages from rawhide are signed incompatibly with F34

6. Are you running any modules that not shipped with directly Fedora's kernel?:
Yes, but unloading them makes no difference

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
(only relevant part)

```
[   37.727622] usb 1-3: new full-speed USB device number 5 using xhci_hcd
[   37.883833] usb 1-3: New USB device found, idVendor=2341, idProduct=0043, bcdDevice= 0.01
[   37.883847] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=220
[   37.883854] usb 1-3: Manufacturer: Arduino (www.arduino.cc)
[   37.883859] usb 1-3: SerialNumber: 85935333537351412201
[   38.517816] cdc_acm 1-3:1.0: ttyACM0: USB ACM device
[   38.520362] usbcore: registered new interface driver cdc_acm
[   38.520367] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[   48.499829] cdc_acm 1-3:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed
```

Comment 1 Ron Isaacson 2021-04-24 22:26:49 UTC
I have the exact same issue with a different device (in my case it's an Aeotec Z-wave stick, connected via USB hub). The acm_port_activate error message is the same. This was working just fine under F32 (5.8.11-200) but started failing last night when I upgraded to F33 (5.11.15-200).

I booted back into 5.8.11 and it started working again. So it seems the error was introduced somewhere between 5.8.11 and 5.11.11.

Comment 2 Ron Isaacson 2021-04-25 07:45:06 UTC
Update: I downloaded a bunch of kernel builds off of koji and here's what I found:

5.10.23 (and below): ok
5.11.11 (and below): ok
5.11.12 (and above): broken

So the problem was introduced between 5.11.11 and 5.11.12. I checked all the way up to 5.11.16 and it's not fixed. Best I can tell, cdc_acm is completely broken in 5.11.12 and above.

I can't be sure but I suspect this commit is the culprit:

https://github.com/torvalds/linux/commit/6069e3e927c8fb3a1947b07d1a561644ea960248

Comment 3 bztdlinux 2021-04-27 06:48:35 UTC
I also just ran into this. Is there an upstream kernel bugzilla issue yet?

Comment 4 dzug.koeln-muenchen 2021-04-30 10:46:24 UTC
Kernel 5.13.0-0.rc0.20210428gitacd3d2859453.2.fc35.x86_64 fixes the bug. (5.12 builds not - even not mainline Linux (custom build))

Comment 5 daniel g. siegel 2021-05-14 11:21:16 UTC
Seems like this is the required patch: https://github.com/torvalds/linux/commit/a8b3b519618f

Upstream kernel bugzilla issue: https://bugzilla.kernel.org/show_bug.cgi?id=212751

Comment 6 Ben Cotton 2022-05-12 15:41:08 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Ben Cotton 2022-06-07 22:31:29 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.