From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215490] New: Logitech Brio doesn't initialise on USB 3.0 port of Asus M5A97 Evo R2.0
Date: Thu, 13 Jan 2022 16:37:48 +0000 [thread overview]
Message-ID: <bug-215490-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215490
Bug ID: 215490
Summary: Logitech Brio doesn't initialise on USB 3.0 port of
Asus M5A97 Evo R2.0
Product: Drivers
Version: 2.5
Kernel Version: 5.15.13
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: nouveau@spliet.org
Regression: No
Overview:
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
Steps to Reproduce:
- Plug the camera's USB cable into any USB 3.0 SS port on the Asus M5A97 Evo
R2.0
Actual Results:
Error messages in the kernel log
Expected Results:
A functioning webcam
Build Date & Hardware:
- kernel 5.15.13-200.fc35.x86_64
- Asus M5A97 Evo R2.0
- Logitech Brio Pro
Additional Information:
Downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2040321
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-01-13 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 16:37 bugzilla-daemon [this message]
2022-01-13 16:40 ` [Bug 215490] Logitech Brio doesn't initialise on USB 3.0 port of Asus M5A97 Evo R2.0 bugzilla-daemon
2022-01-13 16:41 ` bugzilla-daemon
2022-01-20 11:40 ` bugzilla-daemon
2022-09-24 1:07 ` 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-215490-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.