All, I just looked at the link Pete gave me, and that doesn't really match the symptoms of my oops, unless I mis-read his post. I had the camera grabbing frames every 15 seconds or so for hours, specifically from Apr 1 15:47 to Apr 2 08:30, or about 16.5 hours. That's when the oops happened, and usb-ohci interrupts stopped coming in. So it's doesn't seem to be a hotplug issue, or hardware initialization issue. The camera is plugged into the root hub at the time the USB subsystem is loaded. I'm not fully versed in the internals of the USB or OV511 systems by any means, but it does work for quite awhile, just not continually over longer periods of time. As a point of reference, the number of interrupts fired up to the time of the oops was 4355919. Pete, was that fix included in 2.4.3 final, or is it still in the -ac tree? I looked at the patch and the ov511 source in 2.4.3, and it looks like it was applied, but I certainly could be all wet and can't manually read patches against source. I can grab a recent -ac and try it if anyone's interested in knowing the results of it. Brad On Mon, 2 Apr 2001, Pete Zaitcev wrote: > Brad, > > I think you may be hitting a bug in ov511 that I fixed > some time ago, and submitted to -ac series. See: > http://boudicca.tux.org/hypermail/linux-kernel/2001week12/0715.html > > It would be helpful if you ran klogd with -x and decoded > oops manually, including the value of EIP. > > -- Pete > _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
