public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Johan Kjellander <carljohan@kjellander.com>
To: linux-kernel@vger.kernel.org
Subject: pwc-webcam attached to usb-ohci card blocks on read() indefinitely.
Date: Tue, 05 Mar 2002 02:06:07 +0100	[thread overview]
Message-ID: <3C8419FF.10103@kjellander.com> (raw)

I have a computer with four USB ports, one UHCI-controller on the
motherboard and three OHCI PCI-cards from Lucent Technologies (can't
get the exact make and model until tomorrow, no physical access right now).

Attached to each one of these is an Philips ToUCam pro which uses the pwc
and pwcx modules. (yes, the kernel becomes tainted by the pwcx module)

The camera attached to the UHCI-controller running usb-uhci works just fine,
but the three attached to the OHCI-controllers running usb-ohci don't. After
a random amount of frames being read from a camera the read()-call blocks
indefinitely until the device is closed. Next time the v4l-device is opened
the program can again read frames from the camera but read() always blocks
after some time.

The amount of frames that are successfully read can range from 50 to a
couple of thousand, the amount seems to be totally random. There are no
messages in the logs of any kind when the blocking occurs. It happens with
both read() and mmap(), always on the usb-ohci cards and never on the
usb-uhci onboard controller.

Since we have never seen this problem with these cameras, and we've been
using them for well over a year, so I don't think it is a bug in pwc.o. It
could be flaky hardware, in which case usb-ohci should have a workaround.
It could be that some of the cards are sharing IRQ's but one of the cards
has a differant one, and the UHCI is on the same IRQ as two of the OHCI
cards.

The most probable is that there is a bug somewhere in usb-ohci since we
only see the behaviour with this card/driver combination, or that the
cards are crap.

I've tried both 2.4.17 and 18 with the same result.

The only thing in dmesg is:
pwc Iso frame 1 of USB has error -18

But these messages occur without read() blocking most of the times.

Is there any way to get more info on what is going on in usb-ohci?

/Carl-Johan Kjellander
please Cc me as I'm not subscribing to the list.
-- 
begin 644 carljohan_at_kjellander_dot_com.gif
Y1TE&.#=A(0`F`(```````/___RP`````(0`F```"@XR/!\N<#U.;+MI`<[U(>\!UGQ9BGT%>'D2I
Y*=NX,2@OUF2&<827ILW;^822C>\7!!Z1,!K'B5(6H<SH-"E*TJ3%*/>QI6:7"A>Y?):D2^*U@NCV
R<MOQ=]V(B6>LZYD-_T1U<@3W]A4(^$-W4]A#V")W6#.R"$;IR'@).46BN7$9>5D``#L`


             reply	other threads:[~2002-03-05  1:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  1:06 Carl-Johan Kjellander [this message]
2002-03-05  5:11 ` pwc-webcam attached to usb-ohci card blocks on read() indefinitely Greg KH
2002-03-05 10:45   ` Oliver Neukum
2002-03-05 16:28     ` Dr. Michael Weller
2002-03-05 17:11       ` Carl-Johan Kjellander
2002-03-05 17:04     ` Carl-Johan Kjellander
2002-03-05 17:00       ` Greg KH
2002-03-05 17:22         ` Carl-Johan Kjellander
2002-03-05 10:56   ` Carl-Johan Kjellander
  -- strict thread matches above, loose matches on Subject: below --
2002-03-08 21:03 Thomas Winischhofer
2002-03-08 22:35 ` Greg KH
2002-03-09  3:47   ` Thomas Winischhofer
2002-03-09  7:24     ` Greg KH
2002-03-09  3:46 ` Mark Cooke

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=3C8419FF.10103@kjellander.com \
    --to=carljohan@kjellander.com \
    --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