Bug 1155807 - uvcvideo - stream corruption with USB microscope
Summary: uvcvideo - stream corruption with USB microscope
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-22 21:43 UTC by James
Modified: 2016-11-09 21:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:45:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Sample of corrupt image (260.07 KB, image/jpeg)
2014-10-22 21:43 UTC, James
no flags Details

Description James 2014-10-22 21:43:58 UTC
Created attachment 949583 [details]
Sample of corrupt image

Description of problem:

My USB microscope is generally well-supported by uvcvideo. However when pointed at a complex subject (such as mouse mat) that presumably doesn't JPEG down well, the resulting image gets corrupted (see attachment). Only part of the frame is present and the rest is grey.


[  153.532316] usb 2-1.2: new high-speed USB device number 3 using ehci-pci
[  153.652548] usb 2-1.2: New USB device found, idVendor=0ac8, idProduct=3420
[  153.652560] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  153.652566] usb 2-1.2: Product: Venus USB2.0 Camera
[  153.652571] usb 2-1.2: Manufacturer: Vimicro Corp.
[  153.654646] uvcvideo: Found UVC 1.00 device Venus USB2.0 Camera (0ac8:3420)
[  153.658557] input: Venus USB2.0 Camera as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input19


There are no other error messages. I don't observe this under Windows 7, so I think the hardware's OK.


Version-Release number of selected component (if applicable):
kernel-3.17.1-302.fc21.x86_64
libv4l-1.6.0-1.fc21.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Point microscope at a complex image that (presumably) doesn't compress well.
2. Observe results on screen.

Actual results:
Stream corrupted, as shown in upload.

Expected results:
Nice images.

Additional info:

Comment 1 Justin M. Forbes 2015-01-27 14:59:18 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs.

Fedora 21 has now been rebased to 3.18.3-201.fc21.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 James 2015-01-31 10:28:32 UTC
Still present in kernel-3.18.3-201.fc21.x86_64

Comment 3 Fedora Kernel Team 2015-04-28 18:29:59 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs.

Fedora 21 has now been rebased to 3.19.5-200.fc21.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22.

If you experience different issues, please open a new bug report for those.

Comment 4 James 2015-04-28 18:35:01 UTC
still present in kernel-3.19.4-200.fc21.x86_64

Comment 5 Fedora End Of Life 2015-11-04 12:18:57 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 James 2015-11-08 21:15:04 UTC
still present in kernel-4.2.5-300.fc23.x86_64

Comment 7 Laura Abbott 2016-09-23 19:27:53 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 8 Laura Abbott 2016-10-26 16:45:29 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 9 James 2016-11-09 21:18:07 UTC
I've just seen this on Win10 using their generic uvcvideo driver. Seems like something about the hardware is not entirely compliant.


Note You need to log in before you can comment on or make changes to this bug.