Mailing List Archive

tuner stops recording until reboot
This is a fairly recent problem that I am having. This machine has been
working fine for about 6 years now.

When I have the issue, the tuner stops working all together. Mythtv no
longer records on that specific tuner, LiveTV locks up and the only fix
is to reboot. Some of the other tuners still function however.

Not sure if these messages are related:
Jan 26 21:01:07 mythtv kernel: [344307.990288] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:10 mythtv kernel: [344310.960064] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:13 mythtv kernel: [344313.929838] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:16 mythtv kernel: [344316.899616] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:18 mythtv kernel: [344319.869406] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:22 mythtv kernel: [344323.372477] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:25 mythtv kernel: [344326.342257] ivtv2: DMA TIMEOUT 00000001 0
Jan 26 21:01:28 mythtv kernel: [344329.345369] ivtv2: DMA TIMEOUT 00000001 0

I recently upgraded my processor from an AMD 3200+ single core to a
3800+ dual core. I also had to recompile the kernel to enable SMP.
This may or may not be related but its the only recent changes to this
machine.

My system:
Gentoo
uname = Linux mythtv 2.6.31-gentoo-r6 #6 SMP Wed Dec 22 18:08:38 EST
2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD
GNU/Linux
Motherboard = Asus A8N32-SLI-Deluxe
CPU = AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
2 PVR-500's
ivtv driver version 1.4.1
mythtv version 0.23_alpha24158


Let me know what other information you need.

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
On Wed, Jan 26, 2011 at 6:57 PM, Cory Coager <ccoager@gmail.com> wrote:

> This is a fairly recent problem that I am having. This machine has been
> working fine for about 6 years now.
>
> When I have the issue, the tuner stops working all together. Mythtv no
> longer records on that specific tuner, LiveTV locks up and the only fix is
> to reboot. Some of the other tuners still function however.
>
> Not sure if these messages are related:
> Jan 26 21:01:07 mythtv kernel: [344307.990288] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:10 mythtv kernel: [344310.960064] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:13 mythtv kernel: [344313.929838] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:16 mythtv kernel: [344316.899616] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:18 mythtv kernel: [344319.869406] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:22 mythtv kernel: [344323.372477] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:25 mythtv kernel: [344326.342257] ivtv2: DMA TIMEOUT 00000001
> 0
> Jan 26 21:01:28 mythtv kernel: [344329.345369] ivtv2: DMA TIMEOUT 00000001
> 0
>
> I recently upgraded my processor from an AMD 3200+ single core to a 3800+
> dual core. I also had to recompile the kernel to enable SMP. This may or
> may not be related but its the only recent changes to this machine.
>
> My system:
> Gentoo
> uname = Linux mythtv 2.6.31-gentoo-r6 #6 SMP Wed Dec 22 18:08:38 EST 2010
> x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
> Motherboard = Asus A8N32-SLI-Deluxe
> CPU = AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> 2 PVR-500's
> ivtv driver version 1.4.1
> mythtv version 0.23_alpha24158
>
>
> Let me know what other information you need.
>

I have a similar configuration as you--a 5 year old AMD system on an Asus
mobo with a PVR-500 running Gentoo. I had a bout with the same problem last
year, but the occurrence seems to have slowed down significantly lately
(knock on wood). Apparently it's an old problem that's never been
satisfactorily solved; I came across this old mailing list post that
contains a patch to address the problem (with side effects, natch).
http://ivtvdriver.org/pipermail/ivtv-users/2007-June/006627.html Maybe Andy
has some better ideas.

Hmm... I just had a thought. Now that the ivtv drivers are in-kernel, I
wonder if your kernel version could affect it. I generally keep current with
the stable kernel releases (as long as there's no conficts with, say, lirc).
Right now I'm running 2.6.34-gentoo-r12, but I was running an earlier kernel
when I was having more problems. Might be worth a shot to upgrade and see if
it helps.

Karl
Re: tuner stops recording until reboot [ In reply to ]
On 1/26/2011 9:57 PM, Cory Coager wrote:
> This is a fairly recent problem that I am having. This machine has been working fine for about 6 years now.
>
> When I have the issue, the tuner stops working all together. Mythtv no longer records on that specific tuner, LiveTV locks up and the only fix is to reboot. Some of the other tuners still function however.
>
> Not sure if these messages are related:
> Jan 26 21:01:07 mythtv kernel: [344307.990288] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:10 mythtv kernel: [344310.960064] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:13 mythtv kernel: [344313.929838] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:16 mythtv kernel: [344316.899616] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:18 mythtv kernel: [344319.869406] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:22 mythtv kernel: [344323.372477] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:25 mythtv kernel: [344326.342257] ivtv2: DMA TIMEOUT 00000001 0
> Jan 26 21:01:28 mythtv kernel: [344329.345369] ivtv2: DMA TIMEOUT 00000001 0
>
> I recently upgraded my processor from an AMD 3200+ single core to a 3800+ dual core. I also had to recompile the kernel to enable SMP. This may or may not be related but its the only recent changes to this machine.
>
> My system:
> Gentoo
> uname = Linux mythtv 2.6.31-gentoo-r6 #6 SMP Wed Dec 22 18:08:38 EST 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
> Motherboard = Asus A8N32-SLI-Deluxe
> CPU = AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> 2 PVR-500's
> ivtv driver version 1.4.1
> mythtv version 0.23_alpha24158

I had a similar problem with an AMD Athlon X2 4850e and an ASUS M3N78 Pro mobo. The problem was related to AMD Cool n Quiet. When the kernel's ondemand governor lowered the CPU frequency, it also starved the PCI bus. Apparently, it's an issue with my CPU, and maybe with yours, although not with the Athlon II series. It may be possible to experiment with increasing the minimum CPU frequency to prevent the problem. But I couldn't find a frequency that worked reliably for my configuration, which includes a PVR-150 and a pcHDTV 5500. Plus I found that using Cool n Quiet and the ondemand governor wasn't really reducing the system's energy usage. Readings with a kill-a-watt didn't show much difference when the CPU was scaled down one or two notches. So I just went into the BIOS and disabled Cool n Quiet. Before I made that change last November, the system needed to be rebooted about twice a week, and it's a system that doesn't do a lot of recording. Since I made that change, we ha
ven't had any incomplete or failed recordings.

HTH,
Helen

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
Thank you I have upgraded to 2.6.36-gentoo-r5 and will give it a test drive.

On 01/26/2011 11:39 PM, Karl Newman wrote:
> On Wed, Jan 26, 2011 at 6:57 PM, Cory Coager <ccoager@gmail.com
> <mailto:ccoager@gmail.com>> wrote:
>
> This is a fairly recent problem that I am having. This machine
> has been working fine for about 6 years now.
>
> When I have the issue, the tuner stops working all together.
> Mythtv no longer records on that specific tuner, LiveTV locks up
> and the only fix is to reboot. Some of the other tuners still
> function however.
>
> Not sure if these messages are related:
> Jan 26 21:01:07 mythtv kernel: [344307.990288] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:10 mythtv kernel: [344310.960064] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:13 mythtv kernel: [344313.929838] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:16 mythtv kernel: [344316.899616] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:18 mythtv kernel: [344319.869406] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:22 mythtv kernel: [344323.372477] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:25 mythtv kernel: [344326.342257] ivtv2: DMA TIMEOUT
> 00000001 0
> Jan 26 21:01:28 mythtv kernel: [344329.345369] ivtv2: DMA TIMEOUT
> 00000001 0
>
> I recently upgraded my processor from an AMD 3200+ single core to
> a 3800+ dual core. I also had to recompile the kernel to enable
> SMP. This may or may not be related but its the only recent
> changes to this machine.
>
> My system:
> Gentoo
> uname = Linux mythtv 2.6.31-gentoo-r6 #6 SMP Wed Dec 22 18:08:38
> EST 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> AuthenticAMD GNU/Linux
> Motherboard = Asus A8N32-SLI-Deluxe
> CPU = AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> 2 PVR-500's
> ivtv driver version 1.4.1
> mythtv version 0.23_alpha24158
>
>
> Let me know what other information you need.
>
>
> I have a similar configuration as you--a 5 year old AMD system on an
> Asus mobo with a PVR-500 running Gentoo. I had a bout with the same
> problem last year, but the occurrence seems to have slowed down
> significantly lately (knock on wood). Apparently it's an old problem
> that's never been satisfactorily solved; I came across this old
> mailing list post that contains a patch to address the problem (with
> side effects, natch).
> http://ivtvdriver.org/pipermail/ivtv-users/2007-June/006627.html Maybe
> Andy has some better ideas.
>
> Hmm... I just had a thought. Now that the ivtv drivers are in-kernel,
> I wonder if your kernel version could affect it. I generally keep
> current with the stable kernel releases (as long as there's no
> conficts with, say, lirc). Right now I'm running 2.6.34-gentoo-r12,
> but I was running an earlier kernel when I was having more problems.
> Might be worth a shot to upgrade and see if it helps.
>
> Karl
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
On 01/27/2011 12:46 AM, faginbagin wrote:
> I had a similar problem with an AMD Athlon X2 4850e and an ASUS M3N78
> Pro mobo. The problem was related to AMD Cool n Quiet. When the
> kernel's ondemand governor lowered the CPU frequency, it also starved
> the PCI bus. Apparently, it's an issue with my CPU, and maybe with
> yours, although not with the Athlon II series. It may be possible to
> experiment with increasing the minimum CPU frequency to prevent the
> problem. But I couldn't find a frequency that worked reliably for my
> configuration, which includes a PVR-150 and a pcHDTV 5500. Plus I
> found that using Cool n Quiet and the ondemand governor wasn't really
> reducing the system's energy usage. Readings with a kill-a-watt didn't
> show much difference when the CPU was scaled down one or two notches.
> So I just went into the BIOS and disabled Cool n Quiet. Before I made
> that change last November, the system needed to be rebooted about
> twice a week, and it's a system that doesn't do a lot of recording.
> Since I made that change, we ha
> ven't had any incomplete or failed recordings.
>
> HTH,
> Helen
Thanks I just enabled the performance governor, will see how it works.

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
On Wed, 2011-01-26 at 20:39 -0800, Karl Newman wrote:
> On Wed, Jan 26, 2011 at 6:57 PM, Cory Coager <ccoager@gmail.com>
> wrote:
> This is a fairly recent problem that I am having. This
> machine has been working fine for about 6 years now.
>
> When I have the issue, the tuner stops working all together.
> Mythtv no longer records on that specific tuner, LiveTV locks
> up and the only fix is to reboot. Some of the other tuners
> still function however.
>
> Not sure if these messages are related:
> Jan 26 21:01:07 mythtv kernel: [344307.990288] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:10 mythtv kernel: [344310.960064] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:13 mythtv kernel: [344313.929838] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:16 mythtv kernel: [344316.899616] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:18 mythtv kernel: [344319.869406] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:22 mythtv kernel: [344323.372477] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:25 mythtv kernel: [344326.342257] ivtv2: DMA
> TIMEOUT 00000001 0
> Jan 26 21:01:28 mythtv kernel: [344329.345369] ivtv2: DMA
> TIMEOUT 00000001 0
>
> I recently upgraded my processor from an AMD 3200+ single core
> to a 3800+ dual core. I also had to recompile the kernel to
> enable SMP. This may or may not be related but its the only
> recent changes to this machine.
>
> My system:
> Gentoo
> uname = Linux mythtv 2.6.31-gentoo-r6 #6 SMP Wed Dec 22
> 18:08:38 EST 2010 x86_64 AMD Athlon(tm) 64 X2 Dual Core
> Processor 3800+ AuthenticAMD GNU/Linux
> Motherboard = Asus A8N32-SLI-Deluxe
> CPU = AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> 2 PVR-500's
> ivtv driver version 1.4.1
> mythtv version 0.23_alpha24158
>
>
> Let me know what other information you need.
>
> I have a similar configuration as you--a 5 year old AMD system on an
> Asus mobo with a PVR-500 running Gentoo. I had a bout with the same
> problem last year, but the occurrence seems to have slowed down
> significantly lately (knock on wood). Apparently it's an old problem
> that's never been satisfactorily solved; I came across this old
> mailing list post that contains a patch to address the problem (with
> side effects, natch).
> http://ivtvdriver.org/pipermail/ivtv-users/2007-June/006627.html

The above patch is not good for setups without a problem though.


> Maybe Andy has some better ideas.

I never properly reviewed or tested this patch, but I beleive it has
promise:

http://ivtvdriver.org/pipermail/ivtv-devel/2010-July/006547.html

Feedback from anyone with experiencing symptoms with the time to test
it, is welcome. Although I'm not even sure if it will apply cleanly
anymore, I hope it does. If it doesn't, let me know, and I'll clean it
up. (my time this weekend for linux stuff is scarce.)

Regards,
Andy

> Hmm... I just had a thought. Now that the ivtv drivers are in-kernel,
> I wonder if your kernel version could affect it. I generally keep
> current with the stable kernel releases (as long as there's no
> conficts with, say, lirc). Right now I'm running 2.6.34-gentoo-r12,
> but I was running an earlier kernel when I was having more problems.
> Might be worth a shot to upgrade and see if it helps.
>
> Karl
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
On Sat, 29 Jan 2011 09:08:06 -0500, Andy Walls
<awalls@md.metrocast.net> wrote:
> On Wed, 2011-01-26 at 20:39 -0800, Karl Newman wrote:
>> I have a similar configuration as you--a 5 year old AMD system on an
>> Asus mobo with a PVR-500 running Gentoo. I had a bout with the same
>> problem last year, but the occurrence seems to have slowed down
>> significantly lately (knock on wood). Apparently it's an old problem
>> that's never been satisfactorily solved; I came across this old
>> mailing list post that contains a patch to address the problem (with
>> side effects, natch).
>> http://ivtvdriver.org/pipermail/ivtv-users/2007-June/006627.html
>
> The above patch is not good for setups without a problem though.

Right. Even for systems with this problem, it's a poor fix.
It causes increased CPU load (along with related heat and fan
noise), and recordings made through the external A/V inputs
end up with "tinny" audio that is unusable. It also fills
/var/log/messages with lines of the form:

Jan 17 01:28:34 mythtv kernel: [98942.296769] ivtv0: warn: Invalid
PGM index 178891420 (>= 400)

Another poster reported that disabling "Cool'n'Quiet" in the
BIOS solved the problem, but again, this prevents powernowd
from lowering the CPU clock speed, so more heat and noise.
Not good for a set-top box. I did not test that configuration.

> I never properly reviewed or tested this patch, but I beleive it has
> promise:
>
> http://ivtvdriver.org/pipermail/ivtv-devel/2010-July/006547.html
>
> Feedback from anyone with experiencing symptoms with the time to test
> it, is welcome. Although I'm not even sure if it will apply cleanly
> anymore, I hope it does. If it doesn't, let me know, and I'll clean it
> up. (my time this weekend for linux stuff is scarce.)

Yes! I applied this patch shortly after receiving your message,
and can confirm that my PVR-500 is now happily recording in DMA
mode, with both tuners simultaneously, and the card no longer
locks up. I still get DMA ERRORs in the logs, but the ones with
status bits 00000011 that were previously fatal, are not anymore.

I'd strongly advocate applying the modified error handling patches
to the baseline ivtv-irq.c. Thank you for pointing it out, and of
course to Mike for posting the patch.

--Pete

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
On Sat, 2011-02-19 at 18:51 -0800, Pete wrote:
> On Sat, 29 Jan 2011 09:08:06 -0500, Andy Walls

> > I never properly reviewed or tested this patch, but I beleive it has
> > promise:
> >
> > http://ivtvdriver.org/pipermail/ivtv-devel/2010-July/006547.html
> >
> > Feedback from anyone with experiencing symptoms with the time to test
> > it, is welcome. Although I'm not even sure if it will apply cleanly
> > anymore, I hope it does. If it doesn't, let me know, and I'll clean it
> > up. (my time this weekend for linux stuff is scarce.)
>
> Yes! I applied this patch shortly after receiving your message,
> and can confirm that my PVR-500 is now happily recording in DMA
> mode, with both tuners simultaneously, and the card no longer
> locks up. I still get DMA ERRORs in the logs, but the ones with
> status bits 00000011 that were previously fatal, are not anymore.
>
> I'd strongly advocate applying the modified error handling patches
> to the baseline ivtv-irq.c.

Pete,

I'll try and push it forward this weekend.

Mike,

can you provide a "Signed-off-by: " line for your patch you provided
here:

http://ivtvdriver.org/pipermail/ivtv-devel/2010-July/006547.html

http://www.linuxtv.org/wiki/index.php/Development:_Submitting_Patches#Sign_your_work

> Thank you for pointing it out, and of
> course to Mike for posting the patch.

Pete,

Note that Mike's email pointed to some speculation by me:

http://www.gossamer-threads.com/lists/ivtv/users/40943#40943

that I made in response to some guy name "Pete". Pete had made
an interesting observation about the difference between 0x11 and 0x13
DMA ERROR codes in the first place:

http://www.gossamer-threads.com/lists/ivtv/users/40941#40941

;)

> --Pete

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: tuner stops recording until reboot [ In reply to ]
Hallo, thanks to open the thread because i have subscribe me new to the
mailinglist and have the same problem in januari

i have 2 PVR-350 cards its worked for more than a year with gentoo kernel
2.6.34-gentoo-r12 and older , i have never a problem, but after updating to
2.6.36-gentoo-r5 i have the same problems.

i have tryed to reverse to the old kernel but it doesnt work any more, i had
the same problem with the old kernel and libs now (but i have updated gentoo
fully so it not easy to say with update makes the problem) (and maked no
backup ;-(

Ok on 2 february after googling a found this patch 2010-July/006547.html also
working now for 3 weeks, but it creates also a little problem that the mpeg
recorded file is corrupted and this have little glittjes in the stream for the
audio or the video.

ok the glitch are normal because we are losing dma for a moment but fix makes
its continu to get the stream with this patch, but the questions is there, why
i have never problems before the 2.6.36 kernel, but i havent found a way to go
fully back to a working kernel 2.6.34 to lets the working version analysing
it.

so yes you can for me also do the patches to te ivtv-irq.c file in the main
distribution of ivtv.

kris

On Sunday 20 February 2011 03:51:51 Pete wrote:
> On Sat, 29 Jan 2011 09:08:06 -0500, Andy Walls
>
> <awalls@md.metrocast.net> wrote:
> > On Wed, 2011-01-26 at 20:39 -0800, Karl Newman wrote:
> >> I have a similar configuration as you--a 5 year old AMD system on an
> >> Asus mobo with a PVR-500 running Gentoo. I had a bout with the same
> >> problem last year, but the occurrence seems to have slowed down
> >> significantly lately (knock on wood). Apparently it's an old problem
> >> that's never been satisfactorily solved; I came across this old
> >> mailing list post that contains a patch to address the problem (with
> >> side effects, natch).
> >> http://ivtvdriver.org/pipermail/ivtv-users/2007-June/006627.html
> >
> > The above patch is not good for setups without a problem though.
>
> Right. Even for systems with this problem, it's a poor fix.
> It causes increased CPU load (along with related heat and fan
> noise), and recordings made through the external A/V inputs
> end up with "tinny" audio that is unusable. It also fills
> /var/log/messages with lines of the form:
>
> Jan 17 01:28:34 mythtv kernel: [98942.296769] ivtv0: warn: Invalid
> PGM index 178891420 (>= 400)
>
> Another poster reported that disabling "Cool'n'Quiet" in the
> BIOS solved the problem, but again, this prevents powernowd
> from lowering the CPU clock speed, so more heat and noise.
> Not good for a set-top box. I did not test that configuration.
>
> > I never properly reviewed or tested this patch, but I beleive it has
> > promise:
> >
> > http://ivtvdriver.org/pipermail/ivtv-devel/2010-July/006547.html
> >
> > Feedback from anyone with experiencing symptoms with the time to test
> > it, is welcome. Although I'm not even sure if it will apply cleanly
> > anymore, I hope it does. If it doesn't, let me know, and I'll clean it
> > up. (my time this weekend for linux stuff is scarce.)
>
> Yes! I applied this patch shortly after receiving your message,
> and can confirm that my PVR-500 is now happily recording in DMA
> mode, with both tuners simultaneously, and the card no longer
> locks up. I still get DMA ERRORs in the logs, but the ones with
> status bits 00000011 that were previously fatal, are not anymore.
>
> I'd strongly advocate applying the modified error handling patches
> to the baseline ivtv-irq.c. Thank you for pointing it out, and of
> course to Mike for posting the patch.
>
> --Pete
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users