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#76081 - Astro A20 audio headset require module unload/reload

Attached to Project: Arch Linux
Opened by Xavier Claude (claudex) - Saturday, 01 October 2022, 13:36 GMT
Last edited by Toolybird (Toolybird) - Saturday, 03 December 2022, 23:00 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When plugging the Astro A20 USB audio headset, the audio output is not recognized and dmesg is filled with "usb_set_interface failed" error message. The headset has 2 mode, PS4 and PC that can be changed by pushing on a button on the USB key (only when the key is plugged). If I unload the snd_usb_audio module, I can change the mode on the USB key to "computer mode", then I can reload the the snd_sub_audio module and the headset is correctly recognized and works as expected.


Additional info:
* package version(s)
$ uname -a
Linux dantooine 5.19.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 28 Sep 2022 13:21:25 +0000 x86_64 GNU/Linux

$ pacman -Q linux
linux 5.19.12.arch1-1

* config and/or log files etc.

$ sudo dmesg --since '5 minutes ago'
[ 9213.906393] usb 3-2: new full-speed USB device number 7 using xhci_hcd
[ 9214.060191] usb 3-2: config 1 interface 2 altsetting 1 has 1 endpoint descriptor, different from the interface descriptor's value: 2
[ 9214.069107] usb 3-2: New USB device found, idVendor=9886, idProduct=0047, bcdDevice= 0.00
[ 9214.069121] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9214.069125] usb 3-2: Product: Astro A20
[ 9214.069127] usb 3-2: Manufacturer: Astro Gaming
[ 9219.322016] usb 3-2: 2:1: usb_set_interface failed (-110)
[ 9224.440109] usb 3-2: 2:0: usb_set_interface failed (-110)
[ 9224.442184] usb 3-2: 2:0: usb_set_interface failed (-71)
[ 9224.448352] usb 3-2: 2:1: usb_set_interface failed (-71)
[ 9224.450163] usb 3-2: 2:0: usb_set_interface failed (-71)
[ 9224.453134] usb 3-2: 2:0: usb_set_interface failed (-71)
[ 9224.459359] usb 3-2: 2:1: usb_set_interface failed (-71)
...

After the unload/reload module:

[ 9563.963257] usb 3-2: new full-speed USB device number 8 using xhci_hcd
[ 9564.117638] usb 3-2: config 1 interface 2 altsetting 1 has 1 endpoint descriptor, different from the interface descriptor's value: 2
[ 9564.126596] usb 3-2: New USB device found, idVendor=9886, idProduct=0047, bcdDevice= 0.00
[ 9564.126609] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9564.126613] usb 3-2: Product: Astro A20
[ 9564.126616] usb 3-2: Manufacturer: Astro Gaming
[ 9566.537568] usb 3-2: USB disconnect, device number 8
[ 9566.859710] usb 3-2: new full-speed USB device number 9 using xhci_hcd
[ 9567.022591] usb 3-2: New USB device found, idVendor=9886, idProduct=0045, bcdDevice= 0.00
[ 9567.022604] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9567.022608] usb 3-2: Product: Astro A20
[ 9567.022611] usb 3-2: Manufacturer: Astro Gaming
[ 9567.041411] hid-generic 0003:9886:0045.0004: hiddev96,hidraw1: USB HID v1.00 Device [Astro Gaming Astro A20] on usb-0000:04:00.4-2/input5


* link to upstream bug report, if any

Steps to reproduce:
- Plug the USB receiver for the headset.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 03 December 2022, 23:00 GMT
Reason for closing:  No response
Comment by Toolybird (Toolybird) - Monday, 03 October 2022, 06:55 GMT
If this worked previously then it's a kernel regression [1]. If not, then it's still an upstream kernel problem. For specific hardware issues like this, it's best to report'em upstream.

[1] https://wiki.archlinux.org/title/Kernel#Debugging_regressions
Comment by Xavier Claude (claudex) - Monday, 03 October 2022, 18:13 GMT
Ok, thank you, I'll do that. I opened the bug here because it's explicitly written on the kernel bugtracker to open the bugs in the ArchLinux bugtracker when using ArchLinux.
Comment by Toolybird (Toolybird) - Friday, 04 November 2022, 05:09 GMT
Is this still happening with latest kernels? Any luck reporting upstream?

Loading...