Only options I have for ivtv is ivtv_dynbuf=0. I'm running a pvr-350
and pvr-150mce. The last time this occured (last night), it was able to
recover at some point, but the recording it was starting when it
happened was fouled up with no audio and only 2 seconds of video. Does
anyone think the 0.3.6r manual memory allocation might help? Here's my
/var/log/messages from when it happened:
kernel: saa7115: decoder set picture bright=127 contrast=63
saturation=63 hue=0
last message repeated 3 times
kernel: saa7115: decoder disable output
kernel: saa7115: decoder enable output
kernel: saa7115: decoder set picture bright=127 contrast=63
saturation=63 hue=0
last message repeated 3 times
kernel: saa7115: decoder set size
kernel: ivtv: Setup VBI API header 0x0000bd0d pkts 1 buffs 4 ln 24 sz 1456
kernel: ivtv: Setup VBI start 0x0018ea04 frames 4 fpi 1 lines 0x000000f1
kernel: ivtv: Setup VBI API header 0x0000bd0d pkts 1 buffs 4 ln 24 sz 1456
kernel: ivtv: Setup VBI start 0x0018ea04 frames 4 fpi 1 lines 0x00000140
kernel: saa7115: decoder disable output
kernel: saa7115: decoder enable output
kernel: ivtv: Timeout waiting for data! Encoder buffers have 0x00000000
bytes trans_id = 682.
kernel: ivtv: Check digitizer Sync
kernel: saa7115: status: 0xb1
kernel: ivtv: Trying to restart capture.
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x00000082 with result 0xfffffff0
kernel: ivtv: ENC: Failed stopping capture -16
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000d5 with result 0xfffffff0
kernel: ivtv: ENC: Failed to stop VIMevent notification -16
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000c6 with result 0xfffffff0
kernel: ivtv: No Free Mailbox for cmd 0x000000db after 100 tries!
kernel: ivtv: Mailbox[0] 0x000000dc flags 0x00000003
kernel: ivtv: Mailbox[1] 0x000000d9 flags 0x00000003
kernel: ivtv: Mailbox[2] 0x000000c9 flags 0x00000003
kernel: ivtv: Firmware UNRESPONSIVE when trying cmd 0x000000db!!!
kernel: ivtv: No Free Mailbox for cmd 0x000000dc after 100 tries!
kernel: ivtv: Mailbox[0] 0x000000dc flags 0x00000003
kernel: ivtv: Mailbox[1] 0x000000dc flags 0x00000003
kernel: ivtv: Mailbox[2] 0x000000dc flags 0x00000003
kernel: ivtv: Firmware UNRESPONSIVE when trying cmd 0x000000dc!!!
kernel: ivtv: Setup VBI API header 0x0000bd0d pkts 1 buffs 4 ln 24 sz 1456
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000c8 with result 0xfffffff0
kernel: ivtv: init error 21. Code -16
kernel: ivtv: Setup VBI start 0x00000004 frames 1 fpi 48397 lines 0x000000f1
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000b7 with result 0xfffffff0
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000b7 with result 0xfffffff0
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000b7 with result 0xfffffff0
kernel: ivtv: 1000 ms time out waiting for firmware
kernel: ivtv: Failed api call 0x000000b7 with result 0xfffffff0
kernel: ivtv: 1000 ms time out waiting for firmware
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
