Microsoft® LifeCam HD-6000 takes long time to initialize

[Alexander Lazarević]

I have a Microsoft® LifeCam HD-6000 connected to my computer.
Before I can login using lightdm I have to wait about 15 seconds, when the camera is plugged in. The initialization of the camera seems to block the input. After I logged in there is another delay of about 15 seconds when the initialization of the camera seems to happen again. A workaround is to just unplug the camera and plug it back in when it's needed, but as it worked fine with 13.04 I would be happy to not do the unplug/plugin dance.

I added part of the syslog where this initialization seems to happen.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
NonfreeKernelModules: openafs nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: laza 9303 F.... pulseaudio
 /dev/snd/controlC1: laza 9303 F.... pulseaudio
 /dev/snd/controlC0: laza 9303 F.... pulseaudio
 /dev/snd/pcmC0D0p: laza 9303 F...m pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
Date: Fri Nov 1 22:54:27 2013
HibernationDevice: RESUME=UUID=cf0dde7c-2da5-45ee-9d66-c0e6998cea66
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/hostname-root ro splash quiet
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-22 (10 days ago)
dmi.bios.date: 10/07/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: H55M-LE
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd10/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alexander Lazarević (e11bits)]

I've updated the bios but that doesn't change anything!

> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
P1.80
10/20/2010

[Alexander Lazarević (e11bits)]

I don't know what else to say than my initial description of the problem.

Here is a _quick_ video of the boot/login process WITH the camera connected (on top of the monitor you see the blue light flashing sometimes)

http://youtu.be/J-YolFeccIU

The same boot/login WITHOUT the camera connected

http://youtu.be/7foCozsYaT4

(For both videos please forgive the bad sound and the bad quality)

[penalvch (penalvch)]

Alexander Lazarević, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) 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-rc7

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.

[Alexander Lazarević (e11bits)]

I've did a boot/login with

Linux quadrige 3.12.0-031200rc7-generic #201310271935 SMP Sun Oct 27 23:46:05 UTC 2013 i686 i686 i686 GNU/Linux

and had the same behavior. (I've added syslog2 from that kernel)

Maybe I need to point out again, that in any case the camera is working fine. This bug is all about the disturbing long delay for the initialization of the camera that blocks any login with lightdm.

[Alexander Lazarević (e11bits)]

The behavior changes from kernel v3.9.11-saucy to kernel v3.10-rc1-saucy

[penalvch (penalvch)]

Alexander Lazarević, the next step is to fully commit bisect from v3.9.11-saucy to kernel v3.10-rc1-saucy in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Alexander Lazarević (e11bits)]

Oh boy. I will see what I can do ...

[Alexander Lazarević (e11bits)]

Ok, I cloned ubuntu/ubuntu-saucy.git (ok?) and checked out mybisect.

With git I can find the tag v3.10-rc1, but not the tag for v3.9.11. What do I need to look for?

[penalvch (penalvch)]

Alexander Lazarević, it would be best to switch to mainline kernel bisection following https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_upstream_kernel_versions as the previously mentioned tags exist there.

[penalvch (penalvch)]

Alexander Lazarević, one would not have to map v3.9.11-saucy to kernel v3.10-rc1-saucy as they are already in the mainline designation, except with an extra:
-saucy

git bisect start
git bisect good v3.9.11
git bisect bad v3.10-rc1

[Alexander Lazarević (e11bits)]

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git bisect start
git bisect good v3.9.11
fatal: Needed a single revision
Bad rev input: v3.9.11

[penalvch (penalvch)]

Alexander Lazarević, sorry for the mislead, as that error message means here that the tag is not valid. You would want:
git bisect start
git bisect good v3.9
git bisect bad v3.10-rc1

[Launchpad Janitor (janitor)]

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