[mythtv-users] IVTV driver has stopped responding

[Brian Walter]

scott at tbwifi.ca wrote:
>> Anything in messages in /var/log?  I saw this a lot when I had the
>> infamous DMA timeout issue(s) with the ivtv driver.  Once I got to a
>> version of ivtv that did not have that problem, as well as move my mysql
>> database back to the backend, all of my ivtv issues seem to have
>> disappeared...
>>
>>
>> Brian
>>     
>
> Brian,
>
> What distro are you using and what version of ivtv did you need to get to
> to resolve your issues?  I am almost to the conclusion that 0.7.4 is a
> waste of time.  It would appear that the associated kernel 2.6.17 has some
> major issues with ivtv that are difficult to overcome.  I'll have to have
> a look at my /var/log file later to see if I'm experiencing what you were.
>
> Scott
>   
Scott,

I'm running FC6, with the 0.10.x (svn) of IVTV.  I, too, was about to 
give up, and just live with it, via periodic reboots via script.  The 
svn of IVTV I'm using took care of *all* o the DMA issues, and, once 
those went away, so did the Myth 'driver has stopped responding'.  The 
last bit I had to overcome was the 'application not reading fast enough' 
from IVTV.  That one I made go away by moving my MySQL database back to 
backend.  I'd been running it on another server, in an effort to debug 
other perceived performance issues.

Given that your running 0.7, I'd *definitely*  look in messages log - if 
you see DMA timeouts from the kernel, related to ivtv, investigate 
upgrading the driver.

Hope that helps.

Brian