From: Carl-Johan Kjellander <carljohan@kjellander.com>
To: Greg KH <greg@kroah.com>
Cc: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>,
linux-kernel@vger.kernel.org
Subject: Re: pwc-webcam attached to usb-ohci card blocks on read() indefinitely.
Date: Tue, 05 Mar 2002 18:22:16 +0100 [thread overview]
Message-ID: <3C84FEC8.5080801@kjellander.com> (raw)
In-Reply-To: <3C8419FF.10103@kjellander.com> <20020305051146.GA7075@kroah.com> <200203051612.g25GCtc23752@fachschaft.cup.uni-muenchen.de> <3C84FAB4.7020702@kjellander.com> <20020305170047.GA9388@kroah.com>
Greg KH wrote:
> On Tue, Mar 05, 2002 at 06:04:52PM +0100, Carl-Johan Kjellander wrote:
>
>>Oliver Neukum wrote:
>>
>>>Am Dienstag, 5. März 2002 06:11 schrieb Greg KH:
>>>
>>>
>>>>On Tue, Mar 05, 2002 at 02:06:07AM +0100, Carl-Johan Kjellander wrote:
>>>>
>>>>
>>>>>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)
>>>>>
>>>>>
>>>>As you are using this closed source module, I suggest you take this up
>>>>with that module's author.
>>>>
>>>>
>>>Perhaps you could first ask whether the hang can be reproduced
>>>without that module loaded ?
>>>Secondly, that module is unlikely to cause that kind of trouble.
>>>
>>The problem can be reproduced on a computer that has not loaded pwcx.o
>>after boot. The problem is not caused by pwcx.o at all.
>>
>
> But you are reading from the pwc driver, right?
> Have you asked the author of that driver about this?
Since the problem isn't reproducible on the pwc-camera on the onboard
UHCI controller, I tend to think it isn't a problem with the PWC driver
but with either the hardware or the usb-ohci driver. If 3 out of four
cameras has the same problem, and the fourth doesn't the problem is
easiest to find if you look at the difference between them, the UHCI
vs OHCI controller/drivers.
And I think he is subscribed to this list. I don't want to bother him to
much since he has gotten tons of bugreports that has turned out to be
bugs in uhci.o, usb-uhci.o and usb-ohci.o over the last year.
/Carl-Johan Kjellander
--
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`
next prev parent reply other threads:[~2002-03-05 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 1:06 pwc-webcam attached to usb-ohci card blocks on read() indefinitely Carl-Johan Kjellander
2002-03-05 5:11 ` 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 [this message]
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=3C84FEC8.5080801@kjellander.com \
--to=carljohan@kjellander.com \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=greg@kroah.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