[mythtv-users] mythbackend unresponsive

[Nedim Cholich]

Forgot to mention that this is on PVR500 and that there are many
recording that go through until the error.

I've seen some posts about 'select timeout - ivtv driver has stopped
responding' but nothing definite.

On 7/11/06, Nedim Cholich <nedim.cholich at gmail.com> wrote:
> My search for stable mythtv continues. I am now testing
> 2.6.16-1.2133_FC5smpand ivtv
> 0.6.1 after reading some posts about later ivtv versions.
>
> Every now and then my mythbackend becomes unresponsive. What I mean by that
> is that frontend just sits there when I select watch recordings. I tried the
> same from the backend itself to eliminate network issues. This is what I get
> with 'mythfrontend -v all'
> 2006-07-11 21:50:32.997 Connecting to backend server: 192.168.1.4:6543 (try
> 1 of 5)
> 2006-07-11 21:50:32.998 write -> 14 21      MYTH_PROTO_VERSION 26
> 2006-07-11 21:50:33.010 read  <- 14 13      ACCEPT[]:[]26
> 2006-07-11 21:50:33.024 Using protocol version 26
> 2006-07-11 21:50:33.024 write -> 14 31      ANN Monitor rhino.cholich.net 0
> 2006-07-11 21:50: 33.052 read  <- 14 2       OK
> 2006-07-11 21:50:33.096 write -> 14 21      QUERY_RECORDINGS Play
>
> And then it just sits there.
>
> I see following in the /var/log/messages from earlier same day:
> Jul 11 16:03:16 rhino kernel: ivtv1 warning: IRQ: IVTV_IRQ_DEC_DMA_ERR
> Jul 11 16:10:37 rhino kernel: ivtv1 warning: IRQ: IVTV_IRQ_DEC_DMA_ERR
> Jul 11 16:13:31 rhino kernel: ivtv1 warning: IRQ: IVTV_IRQ_DEC_DMA_ERR
> Jul 11 16:13:34 rhino kernel: ivtv1 warning: ENC: REG_DMAXFER 2 wait failed
> Jul 11 16:13:37 rhino kernel: ivtv1 warning: DEC: REG_ENCSG1LEN wait failed
> Jul 11 16:13:38 rhino kernel: ivtv1 warning: ENC: DMA still Pending while
> stopping capture!
>
> Corresponding mythbackend log from the same time is:
> 2006-07-11 16:00:02.819 TVRec(1): Changing from None to RecordingOnly
> 2006-07-11 16:00:03.209 Started recording: Grounded for Life "Part Time
> Lover": channel 1039 on cardid 1, sourceid 1
> 2006-07-11 16:00: 03.279 Can't enable VBI recording (2)
> 2006-07-11 16:00:03.379 TVRec(2): Changing from None to RecordingOnly
> vbi: Invalid argument
> 2006-07-11 16:00:03.596 Started recording: Globe Trekker "Kenya": channel
> 1060 on cardid 2, sourceid 1
> 2006-07-11 16:00:03.662 Can't enable VBI recording (2)
> vbi: Invalid argument
> select timeout - ivtv driver has stopped responding
>
> Is there any combination of kernel and ivtv that is reliable?
>
> Any help would be appreciated!
>
>