Connecting OmniVision USB camera generates buffer-overrun in tegra-xusb

Hi I am new to this forum and I didn’t find the search function…

barney@nano:~$ head -n 1 /etc/nv_tegra_release

R32 (release), REVISION: 1.0, GCID: 14531094, BOARD: t210ref, EABI: aarch64, DATE: Wed Mar 13 07:46:13 UTC 2019

Once I connect an old Sony Eye Cam to Jetson Nano it freezes the USB stack with the following messages:

Apr 7 20:57:27 nano kernel: [ 298.757487] usb 1-2.3: new high-speed USB device number 20 using tegra-xusb
Apr 7 20:57:27 nano kernel: [ 298.784112] usb 1-2.3: New USB device found, idVendor=1415, idProduct=2000
Apr 7 20:57:27 nano kernel: [ 298.784150] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 7 20:57:27 nano kernel: [ 298.784173] usb 1-2.3: Product: USB Camera-B4.09.24.1
Apr 7 20:57:27 nano kernel: [ 298.784193] usb 1-2.3: Manufacturer: OmniVision Technologies, Inc.
Apr 7 20:57:27 nano kernel: [ 298.792208] gspca_main: ov534-2.14.0 probing 1415:2000
Apr 7 20:57:29 nano kernel: [ 300.803632] usb 1-2.3: current rate 16865 is different from the runtime rate 16000
Apr 7 20:57:29 nano kernel: [ 300.814549] usb 1-2.3: 3:1: cannot get min/max values for control 2 (id 3)
Apr 7 20:57:29 nano mtp-probe: checking bus 1, device 20: “/sys/devices/70090000.xusb/usb1/1-2/1-2.3”
Apr 7 20:57:29 nano mtp-probe: bus: 1, device: 20 was not an MTP device
Apr 7 20:57:29 nano systemd-udevd[7438]: Process ‘/usr/sbin/alsactl -E HOME=/run/alsa restore 2’ failed with exit code 99.
Apr 7 20:57:29 nano kernel: [ 300.986590] usb 1-2.3: current rate 1464 is different from the runtime rate 16000
Apr 7 20:57:29 nano kernel: [ 300.996940] usb 1-2.3: 3:1: cannot get min/max values for control 2 (id 3)
Apr 7 20:57:29 nano pulseaudio[6087]: [pulseaudio] alsa-util.c: Unable to load mixer: Invalid argument
Apr 7 20:57:29 nano kernel: [ 301.069316] usb 1-2.3: current rate 661 is different from the runtime rate 16000
Apr 7 20:57:29 nano kernel: [ 301.079343] usb 1-2.3: 3:1: cannot get min/max values for control 2 (id 3)
Apr 7 20:57:29 nano pulseaudio[6087]: [pulseaudio] alsa-util.c: Unable to load mixer: Invalid argument
Apr 7 20:57:29 nano rtkit-daemon[6088]: Supervising 0 threads of 0 processes of 0 users.
Apr 7 20:57:29 nano rtkit-daemon[6088]: Failed to make ourselves RT: Operation not permitted
Apr 7 20:57:29 nano rtkit-daemon[6088]: Supervising 0 threads of 0 processes of 1 users.
Apr 7 20:57:29 nano rtkit-daemon[6088]: Failed to make ourselves RT: Operation not permitted
Apr 7 20:57:29 nano rtkit-daemon[6088]: Supervising 0 threads of 0 processes of 1 users.
Apr 7 20:57:29 nano rtkit-daemon[6088]: Failed to make ourselves RT: Operation not permitted
Apr 7 20:57:29 nano rtkit-daemon[6088]: Supervising 0 threads of 0 processes of 1 users.
Apr 7 20:57:29 nano rtkit-daemon[6088]: Failed to make ourselves RT: Operation not permitted
Apr 7 20:57:29 nano rtkit-daemon[6088]: Supervising 0 threads of 0 processes of 1 users.
Apr 7 20:57:29 nano rtkit-daemon[6088]: Failed to make ourselves RT: Operation not permitted
Apr 7 20:57:30 nano kernel: [ 301.131530] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint
Apr 7 20:57:30 nano kernel: [ 301.138593] retire_capture_urb: 243 callbacks suppressed
Apr 7 20:57:30 nano kernel: [ 301.138611] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint
Apr 7 20:57:30 nano kernel: [ 301.150958] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint

Hi,
Is the issue specific to the usb camera? Could you try other usb cameras?

Hi Dane,

Sorry for the late answer. I am doing the Nano stuff not fulltime.
I checked with a different camera based on antother chipset -> OK
I am not sure if it is the alsa or the ov534 module which misleads the usb driver.
We have to dig deeper into the usb driver in both cases…

Cheers

PS: Somewhere I have another OmniVision camera. I will revalidate it asap.

This issue just re-emerged today for me; had been successfully utilizing the Playstation3 Eye camera plugged into USB port of Nano, but today I began receiving buffer overrun errors, causing my interactive keyboard session via ssh to hang.

I have tried multiple cameras; all are now demonstrating this error.

I can plug the USB camera into a connected USB keyboard with integrated hub; however, the /dev/video0 device is not created; the device is present for lsusb, but not reflected in dmesg output as it is when inserted directly into board.

Could it be a heat or power issue?

Try moving the cable where it connects to the back of the camera; apparently there is some noise in the line and probably physical damage to the cable connection.

I tried plugging in a Playstation 3 Eye camera into a Nano dev unit for the first time a couple of days ago and I’m having the same problem. It doesn’t seem like it’d be a cable problem for three people, but on the other hand if I had another USB webcam handy I’d test it too, and I’m probably not the only person in that situation.

Hi,
We have verified Logitech USB cameras in each release. By default UVC driver is supported. You may follow the steps:
https://devtalk.nvidia.com/default/topic/1057681/jetson-tx1/logitech-c930e-on-jetson-tx1-very-slow-and-choppy-video/post/5363417/#5363417

Hi,

I have similar problem with audio:

https://devtalk.nvidia.com/default/topic/1069536/jetson-nano/problem-with-an-audio-stream/

I have the exact same problem with the Playstation 3 camera. I managed to get it to work once, but after that anytime I plug it in, it hangs the Tegra.

Looking at Dmesg:

[ 1330.996855] usb 1-2.3: new high-speed USB device number 12 using tegra-xusb
[ 1331.019751] usb 1-2.3: New USB device found, idVendor=1415, idProduct=2000
[ 1331.019760] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1331.019765] usb 1-2.3: Product: USB Camera-B4.04.27.1
[ 1331.019770] usb 1-2.3: Manufacturer: OmniVision Technologies, Inc.
[ 1331.024288] gspca_main: ov534-2.14.0 probing 1415:2000
[ 1333.012010] usb 1-2.3: current rate 16622 is different from the runtime rate 16000
[ 1333.023752] usb 1-2.3: 3:1: cannot get min/max values for control 2 (id 3)
[ 1333.498315] usb 1-2.3: current rate 3890 is different from the runtime rate 16000
[ 1333.508477] usb 1-2.3: 3:1: cannot get min/max values for control 2 (id 3)
[ 1333.597521] usb 1-2.3: current rate 794 is different from the runtime rate 16000
[ 1333.607662] usb 1-2.3: 3:1: cannot get min/max values for control 2 (id 3)
[ 1333.633615] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint
[ 1333.640675] retire_capture_urb: 361 callbacks suppressed
[ 1333.640693] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint
[ 1333.653047] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint
[ 1333.660097] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint
[ 1333.667145] tegra-xusb 70090000.xusb: WARN: buffer overrun event on endpoint

etc.

Until I unplug the device and the then the Tegra starts responding again.

Hi txfurtado,

Please help to open a new topic for this issue. Thanks