Conflict betwen webcam 046d:0840 Logitech QuickCam Express and MX-400 logitech usb mouse

[Marcos]

Binary package hint: linux-source-2.6.20

[See comment 7: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/109691/comments/7]

I have feisty clean installation, when I start Camorama (after install it via synaptic) appears the message "error camorama , unable to capture image". I pressed "Close" and I saw that it appears the following kernel message. It also puts the camorama process in the ininterruptible status. I cant kill the camorama task. When I tried to use the camera with amsn it also crash. (I can't try again until I reboot the system). With feisty live cd also the same crash problem. With edgy always I had no problems. It worked fine.

Kernel : 2.6.20-15-generic
lsusb: Bus 001 Device 003: ID 046d:0840 Logitech, Inc. QuickCam Express

Kernel message:
marcos@deflagmator:~$ camorama

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] Oops: 0000 [#1]

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] SMP

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] CPU: 1

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] EIP: 0060:[<f88f5ef0>] Tainted: P VLI

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] EFLAGS: 00010206 (2.6.20-15-generic #2)

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] EIP is at usb_kill_urb+0x20/0x100 [usbcore]

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] eax: 00000003 ebx: f7203180 ecx: dfcf582c edx: f699a000

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] esi: dfc8038c edi: f7f62114 ebp: f7fe45e4 esp: f699bed0

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] Process camorama (pid: 6871, ti=f699a000 task=c2190a90 task.ti=f699a000)
deflagmator kernel: [ 331.512000] ds: 007b es: 007b ss: 0068

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] Stack: 00001388 c215f600 dfa0fb48 c215f618 dfc80000 00000001 dfc8038c f7f62114

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] f8ae4094 00000000 f7fe4700 dfc80000 f6851180 f8ae61b7 00000008 c0177747

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] 00000000 00000000 f7f62114 df9443c0 f7fe45e4 f6851180 c218fe40 00000000

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] Call Trace:

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [<f8ae4094>] qc_isoc_stop+0x34/0xf0 [quickcam]

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [<f8ae61b7>] qc_v4l_close+0x77/0xb0 [quickcam]

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [__fput+167/400] __fput+0xa7/0x190

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [filp_close+71/128] filp_close+0x47/0x80

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator
Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [do_exit+308/2048] do_exit+0x134/0x800

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [do_page_fault+831/1520] do_page_fault+0x33f/0x5f0

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [do_group_exit+38/128] do_group_exit+0x26/0x80

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9
 kernel: [ 331.512000] [put_files_struct+143/176] put_files_struct+0x8f/0xb0

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] =======================

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] Code: 83 c7 eb e1 8d b4 26 00 00 00 00 57 56 53 89 c3 83 ec 14 e8 f3 6e 9f c7 85 db 0f 84 d5 00 00 00 8b 43 20 85 c0 0f 84 ca 00 00 00 <8b> 40 30 85 c0 0f 84 bf 00 00 00 8d 73 04 89 f0 e8 eb 88 9f c7

Message from syslogd@deflagmator at Tue Apr 24 18:37:41 2007 ...
deflagmator kernel: [ 331.512000] EIP: [<f88f5ef0>] usb_kill_urb+0x20/0x100 [usbcore] SS:ESP 0068:f699bed0

[Javier Jardón (jjardon)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

 Please include the information requested from [WWW] https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.

[Marcos (deflagmator)]

Yes of course, but can you let me know which is the procedure for WEBCAMS
(this, that you told me, is for removable storage)

2007/4/24, Javier Jardón <email address hidden>:
>
> Thanks for taking the time to report this bug. Unfortunately we can't fix
> it, because your description didn't include enough information.
>
> Please include the information requested from [WWW]
> https://wiki.ubuntu.com/DebuggingRemovableDevices as separate attachments.
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Assignee: (unassigned) => Javier Jardón
> Status: Unconfirmed => Needs Info
>
> --
> web camera 046d:0840 Logitech, Inc. QuickCam Express driver crash
> https://bugs.launchpad.net/bugs/109691
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Javier Jardón (jjardon)]

We need this:

The output from the uname -a > uname-a.log command
The output from the lspci -vvn > lspci-vvn.log command
The output from the lspci -vv > lscpi-vv.log command
The output from the dmesg > dmesg.log command (with the webcam connected)
The output of cat /proc/version > proc_version.log command

[Marcos (deflagmator)]

I send to you that you request.

I also send you dmesg(2) after start camorama.
, also lsmod.
And also ps -eF command, when you can see the camorama process in uninterruptible status.

Let me know if you need more information.

[Marcos (deflagmator)]

Thinking more deeper in this problem, I checked what I changed in my system since I installed Feisty. I remembered that I use one new USB mouse since I installed Feisty. If I plug my old mouse (PS2) and I disconnect the new USB one, when I start my camera client program (camorama, amsn, etc) It works perfect.

Then, I found that the USB mouse driver is doing some "interference" in my usb camera driver.

I think is a easy reproducible problem.

I will check if the problem is with the "udev" driver that I'm using with my MX-400 logitech mouse. I send you the Xorg.conf file.

[Javier Jardón (jjardon)]

Hello,

thank yoy for your work, Comment here any progress

[Marcos (deflagmator)]

Finally I had to plug my mouse into the PS2 port to solve the problem (with this confitguration all the feisty installation works perfect) . If I use the USB interface to plug it I can't use the USB webcam. I checked with live CD's (feisty and edgy) and always happens the same crash. The only way to use the webcam is to use the PS2 interface for the mouse. I think that the webcam USB and the USB mouse can't be plugged at the same time. (this is a bug) On the other hand in Windows XP (I only use it to check some of this possible problems) I don't have problems. You should have to investigate this bug, because more people can use webcam and mouse at the same time plugged in the usb interface.

If you need more information please ask me.

Regards from Spain, and thanks for your attention

[Death Master (deathmaster)]

I have the same problem. My Logitech QuickCam Express webcam works fine, unless I plug in my Logitech MX400 mouse. The more I move the mouse, the earlier camorama freezes. Same happens to kopete and ekiga.

[Death Master (deathmaster)]

Not the mouse is important in this bug. I start camorama or any other webcam software. Start watching myself, works fine. But in the moment when I plug in my USB printer (HP) or my USB scanner (Canon), camorama freezes.

[Pelládi Gábor (pelladigabor)]

Confirming this bug.

[Alex F (frase)]

I have the same problem. Logitech USB webcam is ID 046d:0840, mouse is MX400, and I have the same error when I start camorama (the "Oops" etc). I do get a brief flash of what would be the camera capture window, which is all binary garbage, no video signal.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for this particular version of the kernel. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

[Pelládi Gábor (pelladigabor)]

The bug still exists in Gutsy Tribe 5 using the live CD.

[user4 (bqz69)]

I have a problem with my new laptop hp dv 9540 and my two webcameras:
1 built in HP webcam
1 usb logitech webcam.

I have drivers installed for both webcams (I think they are the proper ones, at least the usb webcam driver is ok).

When I booth with my usb mouse, I have no webcam at all.

When I boot without usb mouse, and use my touchpad for mouse movement, i get the usb logitech webcam to work.
In this case, the internal HP webcam does not work.

When i then plug in the usb mouse, the mouse pointer cannot be moved, and the usb webcam does still work.

When I remove both the usb mouse and usb webcam and replug in the mouse, the mouse works again.
When I then try to plug in the usb webcam, and start it I get:
Error: Could not connetct to the video device. Please check connection.

I get the same error when I then try to start the internal webcam.

I have followed some of your communications, and send this, in order to help you solving this usb/usb problems.

[Pelládi Gábor (pelladigabor)]

I solved the issue on Gutsy:
1. downloaded the latest (1.00.18) gspca module source from the web: http://mxhaard.free.fr/spca50x/Download/gspcav1-20070508.tar.gz
2. renamed /lib/modules/2.6.22-14-generic/ubuntu/media/gspcav1/gspca.ko to gspca.ko~
3. make && sudo make install
4. reboot or reload gspca module

According to dmesg, the gspca.ko binary shipped with Ubuntu Gutsy has version 1.00.12.
Please make sure the upstream release will be merged for Hardy. It also adds support for many new devices.

[Marcos (deflagmator)]

Problem still in hady. When I start Camorama the systems hangs completely

[Pelládi Gábor (pelladigabor)]

This surprised me. Hardy uses gspca 1.00.20 as far as I know, and the newer gspca fixed the problem for me on Gutsy. I'm still using Gutsy, so I can't test it with Hardy at the moment.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Andres Mujica (andres.mujica)]

Hi, Marcos. Do you know if this bug is reported upstream?

also is it possible for you to check with Intrepid fully updated and Jaunty alpha?

thanks

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 109691

[Farnaby (farnaby)]

I can confirm that the issue is still there in Jaunty 9.04 exactly the same as it was for previous reporters.

Changed to new per Sergio's request.

[kernel-janitor (kernel-janitor)]

Hi deflagmator,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 109691

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]