Dear James,
Am 17.02.22 um 14:41 schrieb James:
Feb. 17, 2022 06:07:16 Paul Menzel:
On the Dell OptiPlex 5055 connect a Logitech Webcam C270 over USB, Linux 5.10.93 reports the error below:
$ dmesg --level=err
[ 13.739837] usb 3-2: 3:3: cannot set freq 24000 to ep 0x82
What problem do you experience?
https://www.techytalk.info/logitech-e3500-webcam-and-cannot-set-freq-16000-to-ep-0x86/
The user has not informed us about any problems specific related to the
Webcam. But the user experiences desktop session freezes. I think it’s
unrelated to the error message above, but while debugging errors always
distract. So I am wondering, what that error means, and am asking for
advise, how to continue to get rid of it. Is there some
debugging/tracing option, showing the non-spec-compliant behavior, and
which I could send to Logitech?
$ dmesg | grep -e 'usb 3-2' -e input10
[ 4.682834] usb 3-2: new high-speed USB device number 2 using xhci_hcd
[ 12.268308] input: C270 HD WEBCAM as /devices/pci0000:00/0000:00:07.1/0000:05:00.3/usb3/3-2/3-2:1.0/input/input10
[ 13.709847] usb 3-2: current rate 16000 is different from the runtime rate 32000
[ 13.725839] usb 3-2: current rate 24000 is different from the runtime rate 16000
[ 13.739837] usb 3-2: 3:3: cannot set freq 24000 to ep 0x82
[ 13.864837] usb 3-2: set resolution quirk: cval->res = 384
[ 59.598714] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 3921.003081] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 3926.523106] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 413c:301a Dell Computer Corp.
Bus 001 Device 003: ID 413c:2113 Dell Computer Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
What does that error mean exactly, and what can be done about it? Could the message be extended like “Report that problem to the USB device vendor to fix the firmware to be spec compliant.” or something like that? (If that is the case.)
Kind regards,
Paul
