On 5/18/07, Brian L. Walter <[EMAIL PROTECTED]> wrote: > John Drescher wrote: > > On 5/2/07, Brian Walter <[EMAIL PROTECTED]> wrote: > > > >> Greetings, > >> > >> I'm working on getting the last few issues cleaned up with a MythTV > >> setup. One of the issues I have, is that whenever I access the first > >> tuner on my PVR-500, I get a series of DMA warnings/errors: > >> > >> May 1 00:06:08 mythtvserver1 kernel: ivtv1 warning: ENC DMA ERROR b > >> May 1 00:06:08 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 0 -> 128 > >> May 1 00:06:08 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 128 -> 104 > >> May 1 00:06:10 mythtvserver1 kernel: ivtv1 warning: ENC DMA ERROR b > >> May 1 00:06:10 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 104 -> 128 > >> May 1 00:06:10 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 128 -> 36 > >> May 1 00:06:15 mythtvserver1 kernel: ivtv1 warning: ENC DMA ERROR b > >> May 1 00:06:15 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 36 -> 128 > >> May 1 00:06:15 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 128 -> 0 > >> May 1 00:06:22 mythtvserver1 kernel: ivtv1 warning: ENC DMA ERROR b > >> May 1 00:06:22 mythtvserver1 kernel: ivtv1 warning: encoder MPEG: > >> offset 0 -> 128 > >> May 1 00:06:22 mythtvserver1 kernel: ivtv1: DMA TIMEOUT 00000001 0 > >> > >> Now, the above seems to only to occur on ivtv1 (the first tuner of the > >> pvr-500). I also have a pvr-150 installed, which consumes ivtv0 (video0). > >> > >> With video0 in use (recording), if I cat from video1 (first tuner), I > >> almost immediately get the above. If I then turn around and cat from > >> video2 (second tuner), it works fine with no errors. > >> > >> I notice that all three ivtv devices are currently on the same > >> interrupt. Is this a cause for concern? > >> > >> Would moving the cards impact this (the problem, not the interrupts)? > >> > >> Changing the interrupts? > >> > >> Indications of a bad board? > >> > >> All of the above? > >> > >> None of the above? > >> > >> > > Did you solve this? I had to move an old pvr250 from old master > > backend (where it ran for almost a year without a reboot or any > > problems) to a newer box that had one of those pvr500s with the bad > > samsung tuner but now I experience these dma errors and it ends up > > terminating the stream until I reboot which basically means I can not > > use the card. > > John > > > > > Additional thoughts: > > My errors at least seem to be related to the system clock drift. On the > mailing list, there was someone who had a script that ran adjtimex and > stopped and restarted ntpd. If you understand enough to translate his > script to your needs, adjtimex -a might be a help. I've noticed that > the DMA errors decrease/disappear once the system clock is forced back > to some semblance of normalcy. > > http://www.gossamer-threads.com/lists/ivtv/users/35352?search_string=adjtimex;#35352 > > Good luck! > > This is one big annoyance factor....I *hope* the PIO/IRQ fix that is due > this weekend corrects this...and I can begin debuging other issues with > MythTV. > Thanks for the info. I too tried to upgrade to 0.10.2 but that did not solvev the problem. Here is my long story. I have used this card (pvr250) since 2004 and back then I did not use it as much but eventually I began using ivtv every day on my dual processor athlon mp box and I noticed some glitches (blockyness every so often) in the recordings so I eventually figured out setting it to PIO completely got rid of the problem. Yesterday, apparently that machine died after being up for almost a year without rebooting. It locked up a few seconds after starting a recording and I rebooted it and it soon locked up again. Anyways that was my mythtv master backed and I had to move it to my main desktop which is a much faster dual processor Opteron 850 with 4GB of memory. After moving it I get these dma errors but I did not get them with the pvr500 card that was in that box only I with the pvr 500 (samsung tuner) I suffered from reduced picture (as the pvr 250 is much better). I ordered a new 150 so hopefully that fixes things otherwise I will have to try to fix the old master backend. My other option is to try with PIO again but I know things have changed since the 2.6.13 kernel with ivtv 0.4.7 I had on the old box. I guess I could wait awhile as Hans has this (PIO) on his schedule..
John _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
