You are not logged in.
Pages: 1
Topic closed
When my Logitech C270 webcam is connected, my kernel log gets absolutely polluted with the following message which is generated about every second:
kernel: usb 1-7: reset high-speed USB device number 8 using xhci_hcdI've tried multiple USB ports, both USB 2 and USB 3, but it doesn't seem to make a difference.
The funny thing is, that the webcam seems to work just fine. Even better: when I actually use the webcam, the messages temporarily stop!
FWIW, this is the log when I connect the webcam:
aug 21 14:45:18 Vigil kernel: usb 1-7: new high-speed USB device number 9 using xhci_hcd
aug 21 14:45:18 Vigil kernel: usb 1-7: New USB device found, idVendor=046d, idProduct=0825, bcdDevice= 0.12
aug 21 14:45:18 Vigil kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=2
aug 21 14:45:18 Vigil kernel: usb 1-7: SerialNumber: B9D9E120
aug 21 14:45:18 Vigil kernel: usb 1-7: Found UVC 1.00 device <unnamed> (046d:0825)
aug 21 14:45:18 Vigil kernel: input: UVC Camera (046d:0825) as /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-7/1-7:1.0/input/input40
aug 21 14:45:20 Vigil kernel: usb 1-7: set resolution quirk: cval->res = 384Any ideas?
Offline
I have this same webcam, which if I recall correctly is approaching a double-digit age (I know it's at least 8 years old.) According to this post which was also my initial suspicion, it could be an "electrically marginal" connection. The reason I share this suspicion is because I've happened to use this device over an un-powered USB extension cable in the past, and was told I sounded like a chipmunk! This probably meant that the chipset wasn't receiving sufficient power over USB to power some part of the ADC/DAC circuity; another possible artifact of insufficient power. When I plugged it directly into my PC or a powered USB hub, the problem went away.
In your case, it could stand to reason that the kernel resets go away upon use because the continued communication with the device causes it to pull more current than when idle, thus alleviating it of the "electrically marginal" state mentioned above. My recommendation is to try it with a powered USB hub, and see if this makes any difference. There are also inexpensive Y-cables like this one available, that can allow a USB device to draw power from two separate USB ports, thus theoretically doubling the amount of available current. If for some reason the cabling in your computer is passing less than the standard 5V/0.5A, such a cable could provide similar potential improvements as would a USB hub.
Offline
This is worth a necro. I had this same issue. For me the problem appears to stem from the usb autosuspend. I was getting these repeated messages:
[14328.242490] usb 1-2.3.2: reset high-speed USB device number 17 using xhci_hcd
[14331.935954] usb 1-2.3.2: reset high-speed USB device number 17 using xhci_hcd
[14335.632518] usb 1-2.3.2: reset high-speed USB device number 17 using xhci_hcd
[14339.335843] usb 1-2.3.2: reset high-speed USB device number 17 using xhci_hcd
[14343.039062] usb 1-2.3.2: reset high-speed USB device number 17 using xhci_hcd
[14346.732422] usb 1-2.3.2: reset high-speed USB device number 17 using xhci_hcdI'm running this camera through a powered hub, and I Can see the light flashing on and off every few seconds, so it's turning on and off constantly
to check the autosuspend state run
> cat /sys/bus/usb/devices/1-2.4.1/power/control
autowhen I set the control to on the repeated messages stop
> echo on | sudo tee /sys/bus/usb/devices/1-2.4.1/power/control
onverify that the messages have stopped, you can even turn it back to auto to double verify.
If this works for you you can make it permanent through udev for the C270 webcam
> cat /etc/udev/rules.d/50-logitech-c270-power.rules
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="046d", ATTR{idProduct}=="0825", TEST=="power/control", ATTR{power/control}="on"you can unplug the device and plug it back in to verify, or run
sudo udevadm control --reload
sudo udevadm trigger --attr-match=idVendor=046d --attr-match=idProduct=0825to trigger the new rule.
No more spam, and the power light for that device stays on, YAY!
Last edited by rethnor (Yesterday 06:00:36)
Offline
This is worth a necro.
Maybe not. We don't know whether the causes of the error four years ago were the same and whether this solution would've worked back then.
Mod note: Closing.
Inofficial first vice president of the Rust Evangelism Strike Force
Online
Pages: 1
Topic closed