usb-ohci, ov511, video4linux

From: christophe barbé (christophe.barbe@ufies.org)
Date: Sun Jan 20 2002 - 10:41:19 EST


I've two problems with the 2.4 series that seems to be related.
The common point is the usb-ohci module.

Since 2.4.0, sometimes X loose the usb mouse. X show nothing special in
its log and the kernel nothing (I have compiled the usb debug code).
This seems to appear when the CPU is mostly used for another application
(most of the time the CPU is 100% used when I loose the mouse).
If I switch to the console (Ctrl-Alt-F1) and switch back to X, the usb
mouse is back. My first thought was that it was a X bug. But the other
problem I have seems to indicate this is a kernel problem.

I bought a usb webcam (D-Link DCS100) which uses the ov511 chipset
familly. I use the last driver (not the one shipped with the kernel) but
I think this is not an issue.
Now It works for a few seconds (minutes) and the application using it
freeze. If I kill the app and retsart it, I works for a few seconds (it
looks like X and the mouse).
Here also it seems to appear when another app use most of the CPU.

The Xawtv outputs are interesting :

# xawtv
This is xawtv-3.68, running on Linux/i586 (2.4.17)
/dev/video0 [v4l]: no overlay support
v4l-conf had some trouble, trying to continue anyway
v4l: timeout (got SIGALRM), hardware/driver problems?
ioctl: VIDIOCSYNC(0): Appel système interrompu
v4l: timeout (got SIGALRM), hardware/driver problems?
ioctl: VIDIOCSYNC(1): Appel système interrompu

What do you think about it ?

I've enabled 'Allow IRQ during APM bios calls'. It seems slighly better
for the mouse but not significantly enough to be sure.

I've tried to boot without apm (apm=off) but problems are still there.

Should I try a preemt or low-latency kernel ?

Christophe

-- 
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8  F67A 8F45 2F1E D72C B41E

Dogs believe they are human. Cats believe they are God.


- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Wed Jan 23 2002 - 21:00:37 EST