Spca5xx not working

Bug #36226 reported by Mark Baas
48
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

I had spca5xx working, but when i updated from (i think) 12 to 13. It stopped
working. I cannot get any trace. There is nothing in dmesg neither there is
in /var/log/syslog. Maybe i has to do with the external-drivers-usb-media_pwc:
Updated USB PWC driver (10.0.8). I saw in the changelog.

I hope you can fix...

Mark

Revision history for this message
Stéphane Marguet (stemp) wrote :

Same here

Revision history for this message
Mark Baas (eljefe123) wrote :

I see you fix the spca5xx driver. It works now, but as soon as i start a program
that makes use of the driver, gnomemeeting e.g. The system hangs (freezes).

Revision history for this message
Julien Olivier (julo) wrote :

I can confirm the freezing of the system when using my webcam.

Revision history for this message
Ben Collins (ben-collins) wrote :

Please see:

https://wiki.ubuntu.com/DebuggingSystemCrash

And try to get some more information regarding this crash, thanks.

Revision history for this message
Stéphane Marguet (stemp) wrote :

I'll like to help you, but I don't know any software or command using the
spca5xx driver without X.
My Webcam is working on Hoary, and was on Breezy Colony 3.

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

I don't know where to post this, #14566 or here, both bugs seem i identical. i
got the lockup too, 2.6.12-9-386.
I got a screenshot when running gnomemeeting on X and quickly switching to a
text console. I'll post it now.

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

Created an attachment (id=4166)
stacktrace of the lockup

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

btw, you surely know this, but i read on internet that that driver is
incompatible with gcc4 and must be built with gcc3.4.

Revision history for this message
Ben Collins (ben-collins) wrote :

(In reply to comment #6)
> I don't know where to post this, #14566 or here, both bugs seem i identical. i
> got the lockup too, 2.6.12-9-386.
> I got a screenshot when running gnomemeeting on X and quickly switching to a
> text console. I'll post it now.

Thanks for the trace. I wish I could see the couple of lines that got missed.
Any chance you could boot with a better resolution that has more lines on the
console? It's sort of important, because I need to know the exception type (NULL
deref, scheduling in IRQ, etc...).

Atleast I know where the problem is occuring.

Can you try one thing:

rmmod spca5xx
modprobe spca5xx compress=0

And retry the test? Maybe compression isn't as stable as it needs to be.

Revision history for this message
Ben Collins (ben-collins) wrote :

(In reply to comment #8)
> btw, you surely know this, but i read on internet that that driver is
> incompatible with gcc4 and must be built with gcc3.4.

All of our kernels and associated modules are compiled with gcc-3.4. Try: cat
/proc/version

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

I'll just add that in hoary i self-compiled that module (spca5xx-20050328) and
it was very stable with my webcam on the hoary kernel. before upgrading my
kernel i uninstalled it.
i'll try to get better resolution and the compression trick.

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

Created an attachment (id=4169)
complete stack trace

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

Created an attachment (id=4170)
it also crashes with no compression. i didn't check if the stacktrace is
different, i attach it too.

Revision history for this message
Mark Baas (eljefe123) wrote :

Yes i have the same kind of trace.
I have compiled with gcc-3.4 (export CC=gcc-3.4), but i think if you compile the module with
gcc-4.0, the system won't hang but the driver will simply not work and the will give the message
that it is compiled with the wrong gcc version.

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

someone on ubuntu-forums claims that he has a procedure producing a working
spca5xx driver on breezy:
http://ubuntuforums.org/showpost.php?p=383244&postcount=21

another person seems to confirm it works:
http://ubuntuforums.org/showthread.php?t=70657&page=4

i'll try it tonight at home (in 8 hours).

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

actually i won't have time to try the method posted on ubuntuforums as i
mentionned. but maybe take a look at it, as it seems to fix the problem for some
users.

Revision history for this message
Mark Baas (eljefe123) wrote :

Yes it works indeed. The only thing i skipped was the:
sudo rm -rf /lib/modules/`uname -r`/kernel/drivers/usb/media/spca5xx*

And after i did that and recompiled it, it worked.

Revision history for this message
Mark Baas (eljefe123) wrote :

no it does not work. I recompiled the driver and it worked. But now i
restarted my computer and i failed again.

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

(in my opinion) it's pretty clear by now that the driver shipped by ubuntu is
simply miscompiled. breezy release date is very soon now, that'd be quite
disappointing to ship a broken driver when a fix is known.

one more person confirmed recompiling fixed the problem:
http://ubuntuforums.org/showpost.php?p=388479&postcount=59

Revision history for this message
Jim (lists-noetzel) wrote :

(In reply to comment #19)
> (in my opinion) it's pretty clear by now that the driver shipped by ubuntu is
> simply miscompiled. breezy release date is very soon now, that'd be quite
> disappointing to ship a broken driver when a fix is known.
>
> one more person confirmed recompiling fixed the problem:
> http://ubuntuforums.org/showpost.php?p=388479&postcount=59

That's me - it was working, now it's not - bug is still valid

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

>> one more person confirmed recompiling fixed the problem:
>> http://ubuntuforums.org/showpost.php?p=388479&postcount=59
>
>That's me - it was working, now it's not - bug is still valid

isn't that possible that when upgrading with apt-get your valid spca5xx was
overwritten with the bad one from ubuntu?

Revision history for this message
Jim (lists-noetzel) wrote :

(In reply to comment #21)
> >> one more person confirmed recompiling fixed the problem:
> >> http://ubuntuforums.org/showpost.php?p=388479&postcount=59
> >
> >That's me - it was working, now it's not - bug is still valid
>
> isn't that possible that when upgrading with apt-get your valid spca5xx was
> overwritten with the bad one from ubuntu?

Quite possible - but I went back and re-installed spca5xx (even tried multiple
versions)

Still have the problem

Revision history for this message
Juan José Rodríguez (juanjorm) wrote :

(In reply to comment #22)
> (In reply to comment #21)
> > >> one more person confirmed recompiling fixed the problem:
> > >> http://ubuntuforums.org/showpost.php?p=388479&postcount=59
> > >
> > >That's me - it was working, now it's not - bug is still valid
> >
> > isn't that possible that when upgrading with apt-get your valid spca5xx was
> > overwritten with the bad one from ubuntu?
>
> Quite possible - but I went back and re-installed spca5xx (even tried multiple
> versions)
>
> Still have the problem

 After the compilation of the spca5xx driver, try:

sudo cp /lib/modules/`uname -r`/kernel/drivers/usb/media/spca5xx.ko
lib/modules/`uname -r`/kernel/drivers/usb/media/spca5xx/spca5xx.ko
sudo modprobe spca5xx GRed=217 GBlue=300 GGreen=224 gamma=4

Good luck!

(sorry: my english is very bad :-( )

Juanjo.

Revision history for this message
pablovp (pablovp86) wrote :

For me, recompiling the driver worked(using GCC 3.4) i followed the instructions
on this link:

http://ubuntuforums.org/showpost.php?p=383244&postcount=21

Thanks

Pablo Valério Polônia

Revision history for this message
Julien Olivier (julo) wrote :

This is fixed for me in Dapper.

Revision history for this message
Ben Collins (ben-collins) wrote :

Claimed fixed in dapper.

Revision history for this message
Gen Zhang (genneth) wrote :

Is there a workaround for people who want to stay with breezy? Dapper seems a
little too un-QA'ed to go to, especially if the machine is not being used by me.
For instance, has it been identified which kernel changes caused the unbreaking?

Revision history for this message
Julien Olivier (julo) wrote :

Sorry but I don't have a clue. All I know is that now it works with Dapper.

Revision history for this message
Ben Collins (ben-collins) wrote :

(In reply to comment #27)
> Is there a workaround for people who want to stay with breezy? Dapper seems a
> little too un-QA'ed to go to, especially if the machine is not being used by me.
> For instance, has it been identified which kernel changes caused the unbreaking?

Sorry. Only security fixes are going into breezy.

Revision history for this message
Gen Zhang (genneth) wrote :

Any chance of going into breezy backports?

Revision history for this message
Trent Lloyd (lathiat) wrote :

This driver does not work for me in dapper, Logitech QuickCam IM
i get the following:

[4303139.966000] drivers/usb/media/spca5xx/spca5xx-main.c: spca5xx driver 00.57.08 registered
[4303353.632000] drivers/usb/media/spca5xx/spca5xx-main.c: init isoc: usb_submit_urb(0) ret -28
[4303353.840000] ohci_hcd 0000:00:02.0: leak ed c233e200 (#81) state 2

iirc this did work in breezy for me

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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