18ec:3299 Can't read uvcvideo (usb video / webcam) device

Bug #1088395 reported by Kzhi
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Attempting to read /dev/video0 for USB video device gives:
libv4l2: error turning on stream: No space left on device

I tested the camera:
Bus 002 Device 006: ID 18ec:3299 Arkmicro Technologies Inc.

The hardware on that machine, is ok. I also have win7 installed and the camera works in it.

I tested this camera on other two machines with Ubuntu 12.10 and it works out of the box (luvcview, guvcview).

I was unable to boot with latest mainline kernels (3.7rc8 or 3.6.9) to test whether the error remains. Although in ArchBang live cd (3.6.9 kernel) the same error still was there when I tried to capture.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: egor 1622 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Dec 10 12:36:30 2012
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
IwConfig:
 ppp0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=6d9d5763-f6e4-4eee-b11a-80964cb90b93 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1202
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7Q57-M DO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1202:bd05/11/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7Q57-MDO:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Kzhi (e-k-orlov) wrote :
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest raring kernel, which can be downloaded from:

https://launchpad.net/ubuntu/+source/linux/3.7.0-6.14/+build/4055554/+files/linux-image-3.7.0-6-generic_3.7.0-6.14_amd64.deb
https://launchpad.net/ubuntu/+source/linux/3.7.0-6.14/+build/4055554/+files/linux-image-extra-3.7.0-6-generic_3.7.0-6.14_amd64.deb

Note you need to install both the linux-image and linux-image-extra packages.

If this bug still exists with the raring kernel, please add the tag: raring

Thanks in advance!

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-bug-exists-upstream
removed: kernel-unable-to-test-upstream
Revision history for this message
Kzhi (e-k-orlov) wrote :

Joseph, just tested it with the latest raring kernel downloaded from the links.
Exactly the same message:
libv4l2: error turning on stream: No space left on device

tags: added: raring
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Ming Lei (tom-leiming) wrote : Re: [Bug 1088395] Re: Can't read uvcvideo (usb video / webcams) devices

Firstly, the uvc video camera is recognized as one full speed device, so
the iso schedule will have to take split transaction which doesn't behave
well on linux.

Secondly, there are so many devices[1] which are connected to the USB
bus 2, and some of them are full speed devices too, so could you connect
your uvc video device to USB bus 1 and see if it can work well?

[1], lsusb
Bus 002 Device 003: ID 1bbb:0000 T & A Mobile Phones
Bus 002 Device 004: ID 0458:003a KYE Systems Corp. (Mouse Systems)
NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 002 Device 005: ID 045e:00dd Microsoft Corp. Comfort Curve
Keyboard 2000 V1.0
Bus 002 Device 006: ID 18ec:3299 Arkmicro Technologies Inc.

Thanks

Revision history for this message
Kzhi (e-k-orlov) wrote : Bug. Can't read uvcvideo (usb video / webcams) devices

Guys, possibly found bug in usb host controller.

Attempting to read /dev/video0 for USB video device gives:
libv4l2: error turning on stream: No space left on device

The camera:
Bus 002 Device 006: ID 18ec:3299 Arkmicro Technologies Inc.

The hardware on that machine, is ok. I also have win7 installed and
the camera works in it.
I tested this camera on other two machines with Ubuntu 12.10 and it
works out of the box (luvcview, guvcview).

I tested it with the latest mainline kernel, the bug still exists.

Here is the link to bug at Ubuntu's launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088395

Necessary files attached.

--
Egor

Revision history for this message
Kzhi (e-k-orlov) wrote : Re: Can't read uvcvideo (usb video / webcams) devices

I tested it with no usb devices plugged in except the camera both on bus 1 and 2 with the same result.

Revision history for this message
Ming Lei (tom-leiming) wrote : Re: [Bug 1088395] Re: Can't read uvcvideo (usb video / webcams) devices

On Mon, Dec 17, 2012 at 1:19 PM, Kzhi <email address hidden> wrote:
> I tested it with no usb devices plugged in except the camera both on bus
> 1 and 2 with the same result.

OK, could you post the 'lsusb -v' on your camera? Also it will be helpful
if you can collect usbmon[1] trace on the device(it is better to only connect
the device on one USB bus).

See below link to see how to use usbmon to get the trace(you need to setup
the trace before opening the camera)

http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt

Thanks,

Revision history for this message
Alan Stern (stern) wrote : Re: Bug. Can't read uvcvideo (usb video / webcams) devices

On Mon, 17 Dec 2012, [KOI8-R] ���� wrote:

> Guys, possibly found bug in usb host controller.

This is not a new bug; it has been known for many, many years. The
ehci-hcd driver does not allocate periodic schedules very well for
full-speed and low-speed devices.

> Attempting to read /dev/video0 for USB video device gives:
> libv4l2: error turning on stream: No space left on device
>
> The camera:
> Bus 002 Device 006: ID 18ec:3299 Arkmicro Technologies Inc.
>
> The hardware on that machine, is ok. I also have win7 installed and
> the camera works in it.
> I tested this camera on other two machines with Ubuntu 12.10 and it
> works out of the box (luvcview, guvcview).

Actually, the camera does not seem to be working properly. Did you
notice these lines in the log?

[ 373.762871] usb 1-1.6: new full-speed USB device number 4 using ehci_hcd
[ 373.855116] usb 1-1.6: not running at top speed; connect to a high speed hub

The camera should be running at high speed -- at least, it claims to
support high speed -- but it's only using full speed.

> I tested it with the latest mainline kernel, the bug still exists.

Yes. I'm afraid this bug isn't going to be fixed any time soon.
Fixing it will be a pretty big job; it's not a simple bug.

> Here is the link to bug at Ubuntu's launchpad:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088395
>
> Necessary files attached.

Alan Stern

Revision history for this message
Kzhi (e-k-orlov) wrote :

Alan, thank you for your reply. May be in the future this bug will be
fixed. I understand it's not a simple bug. I will not send any
messages concerning this bug anymore.

When I tested the camera on other two machines running Ubuntu it
showed the same log message but it worked:
     not running at top speed; connect to a high speed hub

Just for interest, found similar bug on launchpad:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088395

Egor

2012/12/17, Alan Stern <email address hidden>:
> On Mon, 17 Dec 2012, [KOI8-R] Егор Орлов wrote:
>
>> Guys, possibly found bug in usb host controller.
>
> This is not a new bug; it has been known for many, many years. The
> ehci-hcd driver does not allocate periodic schedules very well for
> full-speed and low-speed devices.
>
>> Attempting to read /dev/video0 for USB video device gives:
>> libv4l2: error turning on stream: No space left on device
>>
>> The camera:
>> Bus 002 Device 006: ID 18ec:3299 Arkmicro Technologies Inc.
>>
>> The hardware on that machine, is ok. I also have win7 installed and
>> the camera works in it.
>> I tested this camera on other two machines with Ubuntu 12.10 and it
>> works out of the box (luvcview, guvcview).
>
> Actually, the camera does not seem to be working properly. Did you
> notice these lines in the log?
>
> [ 373.762871] usb 1-1.6: new full-speed USB device number 4 using ehci_hcd
> [ 373.855116] usb 1-1.6: not running at top speed; connect to a high speed
> hub
>
> The camera should be running at high speed -- at least, it claims to
> support high speed -- but it's only using full speed.
>
>> I tested it with the latest mainline kernel, the bug still exists.
>
> Yes. I'm afraid this bug isn't going to be fixed any time soon.
> Fixing it will be a pretty big job; it's not a simple bug.
>
>> Here is the link to bug at Ubuntu's launchpad:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088395
>>
>> Necessary files attached.
>
> Alan Stern
>
>

--
Егор

Revision history for this message
Alan Stern (stern) wrote :

On Wed, 19 Dec 2012, Егор Орлов wrote:

> Alan, thank you for your reply. May be in the future this bug will be
> fixed. I understand it's not a simple bug. I will not send any
> messages concerning this bug anymore.
>
> When I tested the camera on other two machines running Ubuntu it
> showed the same log message but it worked:
> not running at top speed; connect to a high speed hub

The difference is those other two machines have a non-EHCI host
controller (either UHCI or OHCI). Your first machine has only EHCI.

Alan Stern

penalvch (penalvch)
summary: - Can't read uvcvideo (usb video / webcams) devices
+ 18ec:3299 Can't read uvcvideo (usb video / webcam) device
tags: added: latest-bios-1202 needs-upstream-testing regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Kzhi, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run just make a comment to this.

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Kzhi (e-k-orlov) wrote :

I can't test with the latest development release, but this bug still remains in Ubuntu 13.10.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Kzhi, thank you for your comments. Could you please advise on why specifically you can't test the development release? As well, could you please test the live environment of the development release (not install it), and the mainline kernel as requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088395/comments/12 ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Kzhi (e-k-orlov) wrote :

Hi, I have limited internet access on the PC where I can reproduce the bug.
Actually, I can test the dev release but after two weeks or so.
I'll add the comment when done.

Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Moryus (moryus) wrote :
Download full text (4.1 KiB)

Bug is still present in Ubuntu 14.10

guvcview 1.7.3
file guvcview_video.mkv has extension type 1
file guvcview_image.jpg has extension type 0

** (guvcview:28907): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NAtAlIxdm7: Connection refused
file guvcview_image.jpg has extension type 0
Video file suffix detected: 0
Image file suffix detected: 0
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started

(guvcview:28907): Gtk-WARNING **: Theme parsing error: gtk.css:27:35: Junk at end of value

(guvcview:28907): Gtk-WARNING **: Theme parsing error: gtk.css:40:48: Junk at end of value

(guvcview:28907): Gtk-WARNING **: Theme parsing error: gtk.css:48:46: Junk at end of value

(guvcview:28907): Gtk-WARNING **: Theme parsing error: gtk.css:59:58: Junk at end of value

(guvcview:28907): Gtk-WARNING **: Theme parsing error: gtk.css:70:46: Junk at end of value

(guvcview:28907): Gtk-WARNING **: Theme parsing error: gtk.css:81:58: Junk at end of value
video device: /dev/video0
vid:18ec
pid:3290
driver:uvcvideo
device doesn't seem to support uvc H264 (0)
Init. USB2.0 PC CAMERA (location: usb-0000:00:1a.0-1.2)
{ pixelformat = 'MJPG', description = 'MJPEG' }
{ discrete: width = 320, height = 240 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 352, height = 288 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 176, height = 144 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 160, height = 120 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ pixelformat = 'RGB3', description = 'RGB3' }
{ discrete: width = 320, height = 240 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 352, height = 288 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 176, height = 144 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 160, height = 120 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ pixelformat = 'BGR3', description = 'BGR3' }
{ discrete: width = 320, height = 240 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 352, height = 288 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 176, height = 144 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ discrete: width = 160, height = 120 }
 Time interval between frame: 1/30, 1/15, 1/10, 1/5,
{ pixelformat = 'YU12', description = 'YU12' }
{ discrete: width = 320, height = 240 }
 Time interval between fr...

Read more...

Moryus (moryus)
Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Moryus, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.