[ivtv-devel] IVTV driving X to 100% w/o a 350?

[Ryan Steffes]

Since I thought I had finally gotten my PVR150 working by removing the bttv card and moving the PVR150 to a different slot, naturally something else had to pop up to destroy my happiness.  Now, I'm getting random lock ups on the X server.  I don't really understand what's causing it, but it seems to be related to ivtv.  I was trying to get the pvr150 working the latest ivtv drivers, but it was crashing after only a minute or two when a program begins to record.  What was happening is that the CPU usage for X spikes through the roof.  It pegs out at 100% CPU and remains there, with the picture frozen on the screen.  I can't even reboot it because some process is refusing to die.  I can still ssh into the box, and even do memory intensive and disk intensive things (ie, ripping dvds while using mencoder to convert them both locally and on an nfs share) with no problems, but shortly after recording starts it bombs out.   Manually killing the X process with -9 causes the machine to stop responding, but not actually reboot. I tried rolling back to the drivers I was using before I started "improving" things, and it seemed to work, until something apparently made the recording crash about 15 minutes into a show.  With the 0.3.5t driver, just now, the mythbackend usage shot up as well.  

The only thing I can point to that is "wrong" is this:

$ ps aux|grep ivtv
root      6243  0.0  0.0      0     0 ?        S<   20:05   0:00 [ivtv_vbi/0]
root      6244  0.0  0.0      0     0 ?        S<   20:05   0:00 [ivtv_fw/0]
root      6317  0.0  0.0      0     0 ?        S<   20:05   0:00 [ivtv-enc]
root      6318  0.0  0.0      0     0 ?        S<   20:05   0:00 [ivtv-enc-vbi]
mythtv    7449  0.0  0.1   1888   628 pts/2    S+   23:22   0:00 grep ivtv


And I don't know what to do about them.

The only thing I could find similiar was very old messages about using a 350 for video out, which I don't do.

Suggestions?