On Tuesday 24 January 2006 00:22, John Biundo wrote:
> I found these errors in my dmesg output:
>
> ivtv0 warning: ENC: (0) DMA Error 0x0000000b
>
> I found these messages from Hans Verkuil, notably:
> >>Upgrade to the latest ivtv-0.4.2 from the subversion repository. I
> >> think this may well be the same bug as described in ticket 49
> >>(http://ivtvdriver.org/trac/ticket/49). With the latest 0.4.2 from
> >> the svn repository you will see messages like this in the kernel
> >> log:
> >>
> >>ivtv1 warning: ENC: (0) DMA Error 0x0000000b
>
> and:
> >See ticket #49: it also has a workaround for this problem. Still no
> >time to look into this :-(
>
> Looking at ticket #49, I find a workaround that involves modifying
> the source code for ivtv-driver.h
>
> Before I go ahead and do this, it would be great if I could learn:
>
> 1. Is this DMA Error message indicative of a harmful problem? I
> haven't really had any symptoms that sound like what I've read
> related to the error message. However, I'm having some strange
> problems with MythTV, and would like to clear up any ivtv problems
> that might be contributing.
No, it's not a harmful problem in itself. Just that recovering from it
sometimes seems to put the pvr in a strange state. Haven't had time to
investigate really closely.
>
> 2. What are the possible side effects of implementing this
> workaround? Just want to know what to look out for.
The current method was created AFAIK to fix hangs with the old method.
The problem is that the current method may no longer be needed and that
the old method works fine now. I don't know. Try it.
> 3. These errors never appeared (that I recall) before ivtv 0.4.2.
> Does that mean that there's a NEW problem, or is it just that the
> problem existed but was never revealed with an error message before
> 0.4.2? In other words, did installing 0.4.2 introduce a new problem,
> or is it just exposing a problem that was hidden before?
AFAIK these problems appeared around 0.4.0. But they may have been
around before that too. It's definitely not related to 0.4.2.
Note that in 0.4.1 the inputs changed, so that when migrating from 0.4.0
you must take care to update the inputs in MythTV. See ivtv README.
Hans
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
