[mythtv-users] mythbackend crashes... I think because of problems speaking to ivtv

[and]

I'm using an epia m10K with a pvr250-rev1 card. running kernel 
2.4.20-8, with cvs ivtv driver from 2 weeks ago.

For awhile I've been trying to figure out why I have to restart 
mythbackend as well as probe sound separately in my rc.local after a 
reboot. Otherwise I get a crashed backend and a black screen on the 
mythfrontend  when I go to livetv, that I can't get out of.... Today 
this isn't even enough, but it's also exceptionally hot here is San 
francisco 100F, so it could be the heat...

This is the block that keeps repeating in mythbackend.log that I get 
when my backend crashed:

Backend stuffed up in RequestRingBufferBlock
error reading from: /dev/video0
read: Input/output error
error reading from: /dev/video0
read: Input/output error
error reading from: /dev/video0
read: Input/output error
error reading from: /dev/video0
read: Input/output error
error reading from: /dev/video0
read: Input/output error

An this snippet contain the ivtv errors from my messages log:

Sep 12 22:47:00 epia kernel: mtrr: 0xd8000000,0x2000000 overlaps 
existing 0xd8000000,0x800000
Sep 12 22:47:01 epia kernel: ivtv: ivtv-api.c: unknown ioctl 0x400876cd
Sep 12 22:47:01 epia kernel: ivtv: ivtv-api.c: unknown ioctl 0x400876cd
Sep 12 22:47:01 epia kernel: via_v4l: Revision:3
Sep 12 22:47:01 epia kernel: ivtv: ivtv-api.c: unknown ioctl 0x803c7601
Sep 12 22:47:01 epia kernel: ivtv: ivtv-api.c: unknown ioctl 0x400876cd
Sep 12 22:47:01 epia kernel: ivtv: ivtv-api.c: unknown ioctl 0x400876cd
Sep 12 22:47:05 epia gdm-autologin(pam_unix)[4104]: session opened for 
user mythtv by (uid=0)
Sep 12 22:53:52 epia modprobe: modprobe: Can't locate module 
sound-slot-0
Sep 12 22:53:53 epia modprobe: modprobe: Can't locate module 
sound-slot-0
Sep 12 22:53:53 epia kernel: saa7115[0]: decoder set size
Sep 12 22:53:53 epia kernel: Hpsc: 0x00001, Hfsc: 0x00600
Sep 12 22:53:53 epia kernel: Setting full NTSC height
Sep 12 22:53:54 epia kernel: ivtv: init error 1. Code -16
Sep 12 22:53:55 epia kernel: ivtv: init error 2. Code -16
Sep 12 22:53:56 epia kernel: ivtv: init error 3. Code -16
Sep 12 22:53:57 epia kernel: ivtv: init error 4. Code -16
Sep 12 22:53:58 epia kernel: ivtv: init error 5. Code -16
Sep 12 22:53:59 epia kernel: ivtv: init error 6. Code -16
Sep 12 22:54:00 epia kernel: ivtv: init error 7. Code -16
Sep 12 22:54:01 epia kernel: ivtv: init error 8. Code -16
Sep 12 22:54:02 epia kernel: ivtv: init error 9. Code -16
Sep 12 22:54:03 epia kernel: ivtv: init error 10. Code -16
Sep 12 22:54:04 epia kernel: ivtv: init error 11. Code -16
Sep 12 22:54:05 epia kernel: ivtv: init error 12. Code -16
Sep 12 22:54:06 epia kernel: ivtv: init error 13. Code -16
Sep 12 22:54:07 epia kernel: ivtv: init error 14. Code -16
Sep 12 22:54:08 epia kernel: ivtv: init error 15. Code -16
Sep 12 22:54:09 epia kernel: ivtv: init error 16. Code -16
Sep 12 22:54:10 epia kernel: ivtv: init error 17. Code -16
Sep 12 22:54:11 epia kernel: ivtv: init error 18. Code -16
Sep 12 22:54:11 epia kernel:
Sep 12 22:54:12 epia kernel: ivtv: init error 20. Code -16
Sep 12 22:54:14 epia kernel: ivtv: startcap error 2. Code -16
Sep 12 22:54:15 epia kernel: ivtv: init error 19. Code -16
Sep 12 22:54:15 epia kernel:
Sep 12 22:54:16 epia kernel: ivtv: startcap error 1. Code -16
Sep 12 22:54:19 epia kernel: ivtv: Timeout waiting for data!
Sep 12 22:54:52 epia last message repeated 11 times
Sep 12 22:55:55 epia last message repeated 21 times
Sep 12 22:56:58 epia last message repeated 21 times
Sep 12 22:58:01 epia last message repeated 21 times
Sep 12 22:58:19 epia last message repeated 6 times
Sep 12 22:58:20 epia kernel: ivtv: stopcap error 1. Code -16
Sep 12 22:58:21 epia kernel: ivtv: stopcap error 2. Code -16
Sep 12 22:58:22 epia kernel: ivtv: EOS interrupt not received! stopping 
anyway.

I used to also see a fair bit of buffer overruns with mpg-buffers set 
to 30, and have therefore set it to 100 at the moment, and I haven't 
seen them since.

It would seem from these errors that the problem lies between 
mythbackend and the ivtv driver and how they speak to each other or how 
everything loads....

Is there any one who might shed some light on this or have any 
suggestions as to how I might fix it?

thanks

rgds
anders