I had frequent DMA error lockups with r5f1 and a PVR-350. The vast majority of them have been solved by the following:

1) Improving cooling (dunno if this really helped)
2) Setting the PCI latency to 64 for all devices at boot time (dunno if this really helped)
3) Upgrading to IVTV 0.10.5 (this definitely helped)

IVTV 0.10.6 is out now too, which is supposed to have even more DMA fixes. There's no need to upgrade your kernel.

Make sure you back everything up (via dd, etc.) before you start messing with drivers.

I tried to upgrade xdriver too, but only managed to break things, so it's probably best to leave that alone.

Good to know about ivtv, I thought I had to recompile with a newer kernel get latest ivtv. After going to the ivtv site I see now that its in kernels after 2.6.22.

doing the compile, were is good howto. On R5F27 the my make barfs.

===========

make -C driver all
make[1]: Entering directory `/usr/src/ivtv-0.10.6/driver'
make -C /usr/src/linux M=/usr/src/ivtv-0.10.6/driver modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.18-chw-13'
CC [M] /usr/src/ivtv-0.10.6/driver/ivtv-driver.o
In file included from /usr/src/ivtv-0.10.6/driver/ivtv-driver.h:48,
from /usr/src/ivtv-0.10.6/driver/ivtv-driver.c:45:
include/linux/i2c.h:32:26: error: linux/i2c-id.h: No such file or directory
In file included from /usr/src/ivtv-0.10.6/driver/ivtv-driver.c:45:
/usr/src/ivtv-0.10.6/driver/ivtv-driver.h:59:31: error: media/v4l2-common.h: No such file or directory
/usr/src/ivtv-0.10.6/driver/ivtv-driver.h:60:25: error: media/tuner.h: No such file or directory
/usr/src/ivtv-0.10.6/driver/ivtv-driver.h:61:27: error: media/cx2341x.h: No such file or directory
...
...
===============

thanks

You _really_ cannot mix the ivtv 0.10.x drivers with the R5F27 applications (like MythTV) which are compiled against ivtv 1.1.0. There are interface compatibilities in the header files. I don't know how long Cecil spent battling the resulting invasion of chipmunks when this happened during testing but it was _ugly_.

(Edited for clarity about versions.)

My bad; I meant R5F1. I'll update my post. I dunno what the R5F27 situation is.

I am continuing to have the same problem as others on this post. System works well for several days but then one of my two PVR150 won't record. Any recordings made on the glitchy PVR150 are 0 bytes and watch live TV brings you back to the menu. The other tuner continues to work just fine.

The mythbackend log shows:


The last error repeats many times throughout the scheduled recording end time.
Only rebooting seems to make everthing right again. After this the tuner won't record anything. This same thing happens every couple of days. Any ideas?

_________________
LINHES 8.6.1 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 4GB Ram. 1.5TB WD. HDHR Prime. Nvidia GT210. MCE remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote

My lockups have not happened in quite a while now, I think the noapci cleared it up.

Turning off VBI somewhere in mythtv setup menus also has cleared up the some of the VBI issues that I was seeing in my logs.. I have not had the black screen in a while either..

hmmm. Good suggestions on places to look. I'm getting locks on both of my machines.

Two places where I get locked up..
1. System lock-up.. typically after a recording event. (system locked up tight, cold boot. risks filesystem corruption!)
2. PVR350 locks up the screen during watching a recording or edit session of a recording. (I can usually get to a menu where I can "reboot" or SSH in to reboot.)

_________________
// Brian - Hardware:
ASUS P5P800 - P4 3Ghz, 500 GB PATA HD
ASUS P5K-V - P4 Core2 Duo, 500 GB SATA HD
Hauppauge PVR-350, IR Blaster, Comcast Digital Cable
http://tech.groups.yahoo.com/group/KnoppMyth/
KnoppMyth R5F27 >> R5.5