Hans Verkuil wrote, On 05/11/06 17:14:
On Sunday 05 November 2006 23:06, Benjamin M. wrote:
Hi Hans,
Attached the ivtv log from /var/log/messages with the ivtv init and a
"cat /dev/video0 > test.mpg" sequence. I hope it will help...
Ben.
Hans Verkuil wrote, On 05/11/06 13:48:
Please run with ivtv module option 'ivtv_debug=95'. And mail me the
resulting log from /var/log/messages.
Thanks,
Hans
On Sunday 05 November 2006 18:15, Benjamin M. wrote:
Hi!
I've tried with r3521 and now "cat /dev/video0" output absolutely
nothing even after restarting my computer. If there's anything I
can try to help debug the problem let me know.
Ben.
You don't seem to be getting any interrupts at all. What was the last
working version of ivtv (if any)?
Hans
The last working version is r3375, so just before the DMA fix. r3375 works great except for the MythTV time stretch feature, which, in some circumstances, hangs the video output (/dev/video16) while increasing the time stretch speed (Below the related log). This problem seems to be (quite hard to pinpoint so far) triggered by simultaneous recording/playback (can happen without a simultaneous recording.. but recording while increasing the time stretch speed increases the probability) and/or heavy load and/or the disk space available at recording time (file fragmentation?).
Because of this situation with r3375 (and previous revisions), my goal was to try your DMA fix and see if it helps... but I'm facing the "/dev/video0 bug" which is clearly related to changes you have made in r3404 (see http://www.mail-archive.com/[email protected]/msg03429.html and perhaps more interesting http://www.mail-archive.com/[email protected]/msg03435.html). At first limited to changing channel while capturing with r3404... r3521 (or a previous revision... I will have to check) seems to worsen the situation with no output at all on /dev/video0.
I will retry each revision since r3375 with "ivtv_debug=95"... so you will be able to see the evolution between each one...
Ben.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MythTV time stretch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Oct 9 22:00:29 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Oct 9 22:00:29 nfty5600-02 kernel: ivtv0 warning: Failed api call 0x00000003 with result 0xfffffff0
Oct 9 22:00:29 nfty5600-02 kernel: ivtv0 warning: DEC: error changing speed
Oct 9 22:00:29 nfty5600-02 kernel: ivtv0 warning: DEC: error in slow/fast mode
Oct 9 22:00:40 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Oct 9 22:00:40 nfty5600-02 kernel: ivtv0 warning: Failed api call 0x00000015 with result 0xfffffff0
Oct 9 22:00:40 nfty5600-02 kernel: ivtv0 warning: DEC: couldnt read clock
Oct 9 22:00:50 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Oct 9 22:00:50 nfty5600-02 kernel: ivtv0 warning: Failed api call 0x00000015 with result 0xfffffff0
Oct 9 22:00:50 nfty5600-02 kernel: ivtv0 warning: DEC: couldnt read clock
Oct 9 22:01:00 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Oct 9 22:01:00 nfty5600-02 kernel: ivtv0 warning: Failed api call 0x00000015 with result 0xfffffff0
Oct 9 22:01:00 nfty5600-02 kernel: ivtv0 warning: DEC: couldnt read clock
Oct 9 22:01:10 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Oct 9 22:01:10 nfty5600-02 kernel: ivtv0 warning: Failed api call 0x0000000d with result 0xfffffff0
Oct 9 22:01:10 nfty5600-02 kernel: ivtv0 warning: DEC: error pausing
Oct 9 22:01:20 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Oct 9 22:01:20 nfty5600-02 kernel: ivtv0 warning: Failed api call 0x00000003 with result 0xfffffff0
Oct 9 22:01:20 nfty5600-02 kernel: ivtv0 warning: DEC: error changing speed
Oct 9 22:01:20 nfty5600-02 kernel: ivtv0 warning: DEC: error in slow/fast mode
Oct 9 22:01:30 nfty5600-02 kernel: ivtv0 warning: 1000 ms time out waiting for firmware
|
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
