> > Hi Robert, >> >> Start a capture (cat /dev/video0 > foo.mpg ) and then cat >> /proc/interrupts . You should see the interrupts handled for the cx18 >> driver increasing. >> >> If not, then add a debug=0x1ff to the cx18 module options when loading >> the module (or via echo 0x1ff > /proc/modules/cx18/parameters/debug) and >> try another capture. You should get lots of debug in /var/log/messages >> which might give insight into the problem. >> >> And for the record, top-posting is _not_ preferred. But in an era of >> lame smartphone email clients it is forgivable. ;) >> >> Regards, >> Andy >> >> > That certainly provided a lot of additional messages, though from what > I've read, some may be normal, e.g.: > [ 454.856839] cx18-0: irq: sending interrupt SW1: 8 to send > CX18_CPU_DE_SET_MDL > [ 454.868754] cx18-0: warning: failed to be awakened upon RPU > acknowledgment sending CX18_CPU_DE_SET_MDL; timed out waiting 12 msecs > [ 454.868788] cx18-0: api: CX18_CPU_DE_SET_MDL cmd 0x20040005 args > 0x00000001 0x00dc0cd0 0x00000001 0x00000004 0x00008000 > > I'm not sure what constitutes a problem. I'd post log output but it's > about 650 lines from when I modprobed with debug to when I ended capture. > Should I go ahead and send it? > > -Robert >
Possibly relevant ... appeared after ending the capture: [ 492.889079] cx18-0: info: User stopped encoder MPEG [ 492.889084] cx18-0: file: read 32768 from encoder MPEG, got -4 [ 492.889146] cx18-0: ioctl: close() of encoder MPEG [ 492.889150] cx18-0: ioctl: close() of encoder MPEG [ 492.889152] cx18-0: info: close stopping capture [ 492.889154] cx18-0: info: close stopping IDX capture [ 492.889156] cx18-0: info: Stop Capture That's definitely not all that's in there, but the particular line that looks unusual to me is the "file: read 32768 ..." -Robert
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
