Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#70593 - cdc_acm 2-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed

Attached to Project: Arch Linux
Opened by Niccolò Belli (darkbasic) - Monday, 26 April 2021, 13:54 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 06 May 2021, 13:08 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I'm not sure what could be the issue here, but my Aeon Labs Zwave USB stick doesn't work anymore since a couple of weeks and I get the followind in dmesg:

[ 193.677337] usb 2-2: new full-speed USB device number 5 using xhci_hcd
[ 193.818112] usb 2-2: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 193.818117] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 194.372999] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
[ 194.373197] usbcore: registered new interface driver cdc_acm
[ 194.373199] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 200.173616] cdc_acm 2-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed

In zwavejs2mqtt:

INFO ZWAVE: Controller status: Driver: Error: Input/output error, cannot open /dev/ttyACM0

[niko@arch-laptop ~]$ stat /dev/ttyACM0
File: /dev/ttyACM0
Dim.: 0 Blocchi: 0 Blocco di IO: 4096 file speciale a caratteri
Device: 5h/5d Inode: 616 Coll.: 1 Tipo device: a6,0
Accesso: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 14/ uucp)
Accesso : 2021-04-26 15:48:36.417243027 +0200
Modifica : 2021-04-26 15:48:36.417243027 +0200
Cambio : 2021-04-26 15:48:36.417243027 +0200
Creazione: -
[niko@arch-laptop ~]$ cat /etc/group | grep uucp
uucp:x:14:brltty,http,niko
[niko@arch-laptop ~]$ uname -a
Linux arch-laptop 5.11.16-arch1-1 #1 SMP PREEMPT Wed, 21 Apr 2021 17:22:13 +0000 x86_64 GNU/Linux

If I use a Fedora 34 live usb everything works flawlessly.
Last time I tried it on Arch was on April 8th and it worked flawlessly, so some update must have broke it after that day.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 06 May 2021, 13:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.12.1
Comment by Niccolò Belli (darkbasic) - Monday, 26 April 2021, 14:41 GMT
I've also tried an LTS kernel (5.10.32-1-lts) but it didn't help, so it must be something else.
Comment by Niccolò Belli (darkbasic) - Monday, 26 April 2021, 18:47 GMT
Thanks to snapper's btrfs rootfs snapshots I managed to bisect it to the following snapshots
- 26415 5th of April WORKING
- 26556 13th April NOT WORKING

I diffed pacman -Q | sort between the two snapshots and didn't find anything interesting, except that linux moved from 5.11.11-arch1-1 to 5.11.13-arch1-1. So I decided to try downgrading to 5.11.11-arch1-1 and it worked! I also tried 5.11.12-arch1-1 and it didn't work, so that's the first version which breaks it.
Since Fedora 34 uses 5.11.16 and works well, while Arch's 5.11.12+ doesn't (and Arch linux-lts doesn't work as well!) it must be either an Arch specific patch or an arch specific configuration change.
Comment by Niccolò Belli (darkbasic) - Monday, 26 April 2021, 19:53 GMT
Thanks to snapper's btrfs rootfs snapshots I managed to bisect it to the following snapshots
- 26415 5th of April WORKING
- 26556 13th April NOT WORKING

I diffed pacman -Q | sort between the two snapshots and didn't find anything interesting, except that linux moved from 5.11.11-arch1-1 to 5.11.13-arch1-1. So I decided to try downgrading to 5.11.11-arch1-1 and it worked! I also tried 5.11.12-arch1-1 and it didn't work, so that's the first version which breaks it.
Since Fedora 34 uses 5.11.16 and works well, while Arch's 5.11.12+ doesn't (and Arch linux-lts doesn't work as well!) it must be either an Arch specific patch or an arch specific configuration change.
Comment by Niccolò Belli (darkbasic) - Monday, 26 April 2021, 20:01 GMT
This looks like the only config change happened in Arch Linux between 5.11.11 and 5.11.12: https://github.com/archlinux/svntogit-packages/commit/0b94106e755810659ccd9accfa4821bc3b429d34#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a
No patches have been added/removed as far as I can see
So I guess it's either this or Fedora applied some kind of patch to fix this.
Comment by loqs (loqs) - Monday, 26 April 2021, 20:33 GMT
@darkbasic have you read [1]? Which would match commit 826a02e1e2d1ad93707478f48d07c2882914f841 introduced in 5.11.12 [2]
Edit:
Fixed first link

[1] https://lore.kernel.org/linux-usb/bug-212751-208809%40https.bugzilla.kernel.org%2F/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=826a02e1e2d1ad93707478f48d07c2882914f841
Comment by Niccolò Belli (darkbasic) - Thursday, 06 May 2021, 08:59 GMT
Fixed in 5.12.1

Loading...