On Thu, May 18, 2000, Bill Maidment <[EMAIL PROTECTED]> wrote:
> At 10:48 am 18/05/00, Mark McClelland wrote:
>
> > > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error:
> > [3] len=201, status=-63
> > > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error:
> > [7] len=393, status=-63
> > > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error:
> > [8] len=652, status=-63
> >
> ><SNIP>
> >This is an error that I have not seen before. I have seen similar errors
> >when unplugging the camera during capture but they only happen once or
> >twice and then stop. The randomness of the packet lengths makes me
> >suspect that there is a hardware problem somewhere, such as a pin that
> >is not making good contact. I don't know enough about USB's failure
> >modes to say for sure though.
>
> Mark
>
> I had this problem using a LifeView RoboCam right up to 2.3.99-pre8
>
> In 2.3.99-pre9-2 it stopped happening, so I assume there was something
> hogging CPU and/or USB bus that was fixed in pre9-2.
This person was having problems with 2.2.15 which is highly odd.
This doesn't look like a problem with hogging the USB bus. Isochronous
transfers are scheduled first and are pretty much guaranteed to finish
fine before the frame finishes. You usually get errors other than this.
Like I mentioned in my other email, it looks like the system bus is
being hogged by something.
JE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
