uvcvideo fails to init camera and then dmesg is full with traces

Bug #1655878 reported by anatoly techtonik
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The dmesg log should be attached. Camera doesn't work. It worked once when I first plugged it and run guvcview (cheese couldn't find it). Offending lines:

[ 184.760036] usb 2-4: new high-speed USB device number 2 using ehci-pci
[ 184.936757] usb 2-4: New USB device found, idVendor=0ac8, idProduct=3420
[ 184.936762] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 184.936765] usb 2-4: Product: Vimicro USB2.0 Camera
[ 184.936768] usb 2-4: Manufacturer: Vimicro Corp.
[ 185.096698] media: Linux media interface: v0.10
[ 185.137703] Linux video capture interface: v2.00
[ 236.272492] usbcore: registered new interface driver snd-usb-audio
[ 236.273934] uvcvideo: Found UVC 1.00 device Vimicro USB2.0 Camera (0ac8:3420)
[ 236.291047] uvcvideo 2-4:1.0: Entity type for entity Processing 2 was not initialized!
[ 236.291054] uvcvideo 2-4:1.0: Entity type for entity Camera 1 was not initialized!
[ 236.291057] uvcvideo 2-4:1.0: Entity type for entity Extension 4 was not initialized!
[ 236.291781] input: Vimicro USB2.0 Camera as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/input/input14
[ 236.303796] usbcore: registered new interface driver uvcvideo
[ 236.303799] USB Video Class driver (1.1.1)
[ 256.624304] usb 2-4: USB disconnect, device number 2
[ 256.648053] ------------[ cut here ]------------
[ 256.648063] WARNING: CPU: 1 PID: 6752 at /build/linux-RZGRu0/linux-4.8.0/fs/sysfs/group.c:237 sysfs_remove_group+0x8b/0x90
[ 256.648065] sysfs group ffffffff9c8d04a0 not found for kobject 'event14'

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: techtonik 6121 F.... pulseaudio
 /dev/snd/controlC0: techtonik 6121 F.... pulseaudio
Date: Thu Jan 12 11:40:54 2017
HibernationDevice: RESUME=UUID=89bb43be-f25f-4caa-9f0c-7bb67d5f5583
MachineType: System manufacturer P5KR
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=8814b3f6-00a6-45a7-a112-afd933fdc5b5 ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-34-generic N/A
 linux-backports-modules-4.8.0-34-generic N/A
 linux-firmware 1.161.1
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-20 (84 days ago)
dmi.bios.date: 06/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KR
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd06/26/2008:svnSystemmanufacturer:pnP5KR:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KR:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5KR
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
anatoly techtonik (techtonik) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
anatoly techtonik (techtonik) wrote :

I don't remember that I tried to use this camera before.

Trying to follow the instructions at https://wiki.ubuntu.com/KernelMainlineBuilds - it says to uninstall out-of-tree modules, but doesn't refer to how to identify them and actually uninstall.

There is exactly the same issue at https://unix.stackexchange.com/questions/196616/identify-out-of-tree-modules but provided solution looks more like hack. Maybe it is outdated and there is a better official way to get them?

Revision history for this message
anatoly techtonik (techtonik) wrote :

I failed to run on new kernel - I tried to run linux-image-4.10.0-041000rc4-generic_4.10.0-041000rc4.201701152031_amd64.deb and it just hangs.

I also tried to remove nvidia module and failed.
http://askubuntu.com/questions/875310/where-nvidia-kernel-module-is-hiding

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.