> Has anyone seen this happen to their system?
Yes, this happens regularly on my system:
Apr 4 17:57:39 hush kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Apr 4 17:57:39 hush kernel: ivtv0 warning: Failed api call 0x00000015 with result 0xfffffff0
Apr 4 17:57:39 hush kernel: ivtv0 warning: DEC: couldnt read clock
Apr 4 17:57:47 hush kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Apr 4 17:57:47 hush kernel: ivtv0 warning: Failed api call 0x00000015 with result 0xfffffff0
Apr 4 17:57:47 hush kernel: ivtv0 warning: DEC: couldnt read clock
Apr 4 17:57:55 hush kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Apr 4 17:57:55 hush kernel: ivtv0 warning: Failed api call 0x0000000d with result 0xfffffff0
Apr 4 17:57:55 hush kernel: ivtv0 warning: DEC: error pausing
Apr 4 17:57:58 hush kernel: ivtv0 warning: No Free Mailbox for cmd 0x00000015 after 100 tries!
Apr 4 17:57:58 hush kernel: ivtv0 warning: Mailbox[0] 0x00000053 flags 0x00000003
Apr 4 17:57:58 hush kernel: ivtv0 warning: Mailbox[1] 0x00000053 flags 0x00000003
Apr 4 17:57:58 hush kernel: ivtv0 warning: Firmware UNRESPONSIVE when trying cmd 0x00000015!!!
Apr 4 17:57:58 hush kernel: ivtv0 warning: DEC: couldnt read clock
Apr 4 17:58:06 hush kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Apr 4 17:58:06 hush kernel: ivtv0 warning: Failed api call 0x0000000d with result 0xfffffff0
Apr 4 17:58:06 hush kernel: ivtv0 warning: DEC: error pausing
Apr 4 17:58:14 hush kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Apr 4 17:58:14 hush kernel: ivtv0 warning: Failed api call 0x00000003 with result 0xfffffff0
Apr 4 17:58:14 hush kernel: ivtv0 warning: DEC: error changing speed
Apr 4 17:58:14 hush kernel: ivtv0 warning: DEC: error in slow/fast mode
Apr 4 17:58:22 hush kernel: ivtv0 warning: 1000 ms time out waiting for firmware
Apr 4 17:58:22 hush kernel: ivtv0 warning: Failed api call 0x00000015 with result 0xfffffff0
Apr 4 17:58:22 hush kernel: ivtv0 warning: DEC: couldnt read clock
Apr 4 17:58:24 hush shutdown: shutting down for system halt
However, I am using a 350, and I accredited the problem to the
combination of using the mpeg2-decoder for playback in combination with
the osd, since it seems to happen mostly when I skip, un-pause or
otherwise cause the osd to appear.
In fact it happened that often that I reverted to not using the 350's
decoding capabilities and use the ivtv-fb for playback now.
Note that I am using a fairly recent (0.4.x) of the driver.
Regards,
Ronald.
well, my errors are occuring when I'm just having the system record shows. No interaction is causing it to happen on my part. Part of why I posted was cause I couldn't find any other postings that resembled what I was encountering.
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
