Created attachment 1850584 [details] Full kernel log. 1. Please describe the problem: When plugging in the Logitech Brio Pro (UVC-compatible) webcam into a USB 3.0 superspeed port, the device doesn't initialise properly. Dmesg contains the following: [ 8014.615870] usb 11-1: new SuperSpeed USB device number 2 using xhci_hcd [ 8019.973226] usb 11-1: unable to read config index 0 descriptor/all [ 8019.973237] usb 11-1: can't read configurations, error -110 [ 8020.269331] usb 11-1: new SuperSpeed USB device number 3 using xhci_hcd [ 8025.644686] usb 11-1: unable to read config index 0 descriptor/all [ 8025.644697] usb 11-1: can't read configurations, error -110 [ 8025.652808] usb usb11-port1: attempt power cycle The same camera works in any of the USB 2.0 ports, albeit without 4K support. On a different machine (Asus PN50), the camera works fine in a USB superspeed port: [222114.302378] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd [222114.320421] usb 3-1: New USB device found, idVendor=046d, idProduct=085e, bcdDevice= 3.17 [222114.320431] usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [222114.320434] usb 3-1: Product: Logitech BRIO [222114.320437] usb 3-1: SerialNumber: 90A3845D [222114.328549] input: Logitech BRIO Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb3/3-1/3-1:1.5/0003:046D:085E.000A/input/input24 [222114.380587] hid-generic 0003:046D:085E.000A: input,hidraw2: USB HID v1.11 Device [Logitech BRIO] on usb-0000:01:00.0-1/input5 [222114.409388] mc: Linux media interface: v0.10 [222114.428046] videodev: Linux video capture interface: v2.00 [222114.459729] usb 3-1: current rate 16000 is different from the runtime rate 24000 [222114.469733] usb 3-1: current rate 16000 is different from the runtime rate 32000 [222114.479730] usb 3-1: current rate 16000 is different from the runtime rate 48000 [222114.531631] usbcore: registered new interface driver snd-usb-audio [222114.531771] usb 3-1: Found UVC 1.00 device Logitech BRIO (046d:085e) [222114.557894] input: Logitech BRIO as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb3/3-1/3-1:1.0/input/input25 [222114.558136] usbcore: registered new interface driver uvcvideo [222114.609743] usb 3-1: current rate 16000 is different from the runtime rate 48000 [222114.629786] usb 3-1: current rate 16000 is different from the runtime rate 48000 [222114.644731] usb 3-1: current rate 16000 is different from the runtime rate 48000 2. What is the Version-Release number of the kernel: 5.15.13-200.fc35.x86_64 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 : Not with other 5.15 kernels. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Plug the camera's USB cable into any USB 3.0 SS port on the Asus M5A97 Evo R2.0 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``: Unknown, but judging by the xhci patches for 5.16 it is unlikely that this makes a difference. This bug probably needs to escalate to upstream. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No.
Hi Roy, So the Asus M5A97 Evo R2.0 motherboard is somewhat old, its chipsets does not support USB-3 at all, so an extra chip with an early XHCI controller has been added on the board. In my experience the early USB-3 controllers sometimes where buggy. So this might just be an incompatibility between the used somewhat old XHCI controller and the quite new webcam. Another possible cause of issues like this is that some of the powerrails on your board might not be fully up2spec anymore (old capacitors) USB3 SuperSpeed tends to be somewhat sensitive to this. BTW with the Asus PN50 are you using a Type-C port there or a Type-A port, I guess the camera comes with a Type-C to -A convertor? That should be fine, but you may want to try a Type-A port on the PN50 to rule it out. Other then my above rambling, I think it would indeed be best to take this upstream, since it is an enumeration issue the right person to email about this would be Mathias Nyman <mathias.nyman> (XHCI maintainer) with linux-usb.org in the Cc. Feel free to Cc me too. Regards, Hans
You're right, USB 3 Superspeed is added using: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller On the Asus PN50 I tried the same USB-A (to USB-C) cable that I used on the M5A97 motherboard. I'll make a report on the kernel bugzilla and link it here. Thanks!
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 '35'. 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 35 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.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.