On Wed, 2011-01-26 at 20:39 -0800, Karl Newman wrote: > On Wed, Jan 26, 2011 at 6:57 PM, Cory Coager <[email protected]> > 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 > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
