On Wed, May 17, 2000, Jerry White <[EMAIL PROTECTED]> wrote:
> Have 2.2.15 kernel with backpatch applied.
> using ov511.o as driver
> below is the message s that I get
> please don't flame Me if the attachment is too long
> a nice "too much" will do
Some of the info isn't needed, but it's alright. I'll snip out the
unneeded info.
> May 17 09:07:34 jerry kernel: usb.c: registered new driver usbdevfs
> May 17 09:07:34 jerry kernel: usb.c: registered new driver hub
> May 17 09:07:34 jerry kernel: uhci.c: USB UHCI at I/O 0xe400, IRQ 11
> May 17 09:07:34 jerry kernel: uhci.c: detected 2 ports
> May 17 09:07:34 jerry kernel: usb.c: new USB bus registered, assigned bus number 1
> May 17 09:07:34 jerry kernel: usb.c: USB new device connect, assigned device number
>1
> May 17 09:07:36 jerry kernel: Product: USB UHCI Root Hub
> May 17 09:07:36 jerry kernel: SerialNumber: e400
> May 17 09:07:36 jerry kernel: hub.c: USB hub found
> May 17 09:07:36 jerry kernel: hub.c: 2 ports detected
> ( I believe that the following occurs when I try to insert
> the ov511.o as module at bootup but NOT sure )
Just to clarify, the messages below (the descriptor dump) occurs when
you plug in the device, or the system gets around to enumerating it
after the USB drivers have started.
> May 17 09:07:39 jerry kernel: usb.c: USB new device connect, assigned device number
>2
> May 17 09:07:39 jerry kernel: usb.c: This device is not recognized by any installed
>USB driver.
> May 17 09:07:39 jerry kernel: Length = 18
> May 17 09:07:39 jerry kernel: DescriptorType = 01
> May 17 09:07:39 jerry kernel: USB version = 1.00
> May 17 09:07:39 jerry kernel: Vendor:Product = 05a9:0511
> May 17 09:07:39 jerry kernel: MaxPacketSize0 = 8
> May 17 09:07:39 jerry kernel: NumConfigurations = 1
> May 17 09:07:39 jerry kernel: Device version = 1.00
> May 17 09:07:39 jerry kernel: Device Class:SubClass:Protocol = 00:00:00
> May 17 09:07:39 jerry kernel: Per-interface classes
[snip]
> The following is when I did an insmod ov511.o
> after system was up and running.
>
> May 17 09:43:22 jerry kernel: ov511: [usb_ov511_init:2701] creating /proc/ov511
> May 17 09:43:22 jerry kernel: usb.c: registered new driver ov511
> May 17 09:43:22 jerry kernel: ov511: [ov511_probe:2539] probing for device...
> May 17 09:43:22 jerry kernel: ov511.c: USB OV511 camera found
> May 17 09:43:22 jerry kernel: Camera: Creative Labs WebCam 3
> May 17 09:43:22 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size: 0,
>mult=0, alt=7
> May 17 09:43:22 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> May 17 09:43:22 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> May 17 09:43:22 jerry kernel: ov511: [ov76xx_configure:2372] I2C synced in 1
>attempt(s)
> May 17 09:43:22 jerry kernel: ov511: Sensor is an OV7610
> May 17 09:43:22 jerry kernel: ov511: [ov511_mode_init_regs:930] width:640,
>height:480, mode:4, sub:0
> May 17 09:43:22 jerry kernel: ov511.c: ov511 driver version 1.13 registered
>
> the below was when I started the
> xawtv program
>
> May 17 09:45:07 jerry kernel: ov511: [ov511_init_isoc:1529] *** Initializing capture
>***
> May 17 09:45:07 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size:
>993, mult=31, alt=1
> May 17 09:45:07 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> May 17 09:45:07 jerry kernel: ov511: [ov511_stop_isoc:1604] *** Stopping capture ***
> May 17 09:45:07 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size: 0,
>mult=0, alt=7
> May 17 09:45:07 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> May 17 09:45:07 jerry kernel: ov511: [ov511_isoc_irq:1502] hmmm... not streaming,
>but got interrupt
> May 17 09:45:07 jerry kernel: ov511: [ov511_isoc_irq:1502] hmmm... not streaming,
>but got interrupt
> May 17 09:45:07 jerry kernel: ov511: [ov511_init_isoc:1529] *** Initializing capture
>***
> May 17 09:45:07 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size:
>993, mult=31, alt=1
> May 17 09:45:07 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> May 17 09:45:08 jerry kernel: ov511: [ov511_mode_init_regs:930] width:64, height:48,
>mode:4, sub:0
> May 17 09:45:08 jerry kernel: ov511.c: Unknown mode (64, 48): 4
> May 17 09:45:09 jerry kernel: ov511: [ov511_mode_init_regs:930] width:320,
>height:240, mode:4, sub:0
> May 17 09:45:09 jerry kernel: ov511: [ov511_mode_init_regs:930] width:320,
>height:240, mode:4, sub:0
> 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
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2] len=714,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [4] len=76,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [5] len=843,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7] len=137,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [8] len=716,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [0] len=268,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [1] len=779,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [5] len=139,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7] len=649,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [0] len=204,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2] len=714,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [1] len=139,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [5] len=587,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7] len=585,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2] len=522,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [3] len=521,
>status=-63
> May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2] len=202,
>status=-63
This is where the problem is.
-63 = -ENOSR = TD_CTRL_DBUFERR is set
All of that means "Data Buffer Error". In this case, there was an
overrun writing data to system memory. I've never actually seen this
error generated before.
This sounds like a hardware problem. Could you give us a description of
your hardware?
Is this machine typically busy?
JE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
