From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: usb or video4linux problem
Date: Thu, 24 Jan 2002 22:28:57 -0500 [thread overview]
Message-ID: <20020125032857.GA671@online.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
I send a mail few days ago about a problem with a usb webcam (Dlink
DCS100). I see the same thing with various webcam apps (gnomemeeting,
gqcam, camstream, xawtv, ...). So clearly it's not a user-level problem.
It can be a hardware one but i'm convinced it is not (or in the OHCI
chip in my toshiba satellite 2520cds).
With all app I can see the stream but suddenly it freezes.
Because of the following output from xawtv when the problem occurs:
v4l: timeout (got SIGALRM), hardware/driver problems?
ioctl: VIDIOCSYNC(0): Appel système interrompu
I have checked out the code and the interesting part in drv1-v4l.c is :
alarms=0;
alarm(SYNC_TIMEOUT);
retry:
if (-1 == (rc = xioctl(h->fd,VIDIOCSYNC,h->buf_v4l+frame))) {
if (errno == EINTR && !alarms)
goto retry;
}
From which I conclude that SYNC_TIMEOUT could be to small. The value is
3 secondes which seems to be quite enough. To be sure I've tried with 30
and got the same thing.
So It's a justified timeout because the nextframe will never be there.
usbview sees the webcam before and after the problem.
Restarting the app is enough to get the stream.
I'm convinced that it's a problem with OHCI.
I think it's a soft problem because I can trigger it with cpu/io
activity.
What can I do to go further ?
Christophe
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
People that hate cats will come back as mice in their next life.
--Faith Resnick
[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]
next reply other threads:[~2002-01-25 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 3:28 christophe barbé [this message]
2002-01-25 4:12 ` usb or video4linux problem Greg KH
2002-01-25 4:39 ` christophe barbé
2002-01-25 4:42 ` christophe barbé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020125032857.GA671@online.fr \
--to=christophe.barbe.ml@online.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox