[mythtv-users] select timeout - ivtv driver has stopped responding

Sat Jun 10 09:06:21 UTC 2006

We'll I compiled the IVTV modules from SVN revision 3339, they load fine:
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.6.2 (development snapshot compiled on Mon May 22
01:17:37 2006) loading
ivtv:  Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS gcc-4.1
ivtv:  In case of problems please include the debug info between
ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
ivtv:  any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 19
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
tveeprom 0-0050: Hauppauge model 26152, rev C599, serial# 8961617
tveeprom 0-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has no radio, has IR remote
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 0-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv:  ====================  END INIT IVTV  ====================

However I'm still getting these messages every couple seconds when I
try and record:
2006-06-10 01:58:29.090 New DB scheduler connection
2006-06-10 01:58:29.091 Connected to database 'mythconverg' at host: localhost
2006-06-10 01:58:29.097 mythbackend version: 0.19.20060121-2 www.mythtv.org
2006-06-10 01:58:29.098 Enabled verbose msgs:  important general
2006-06-10 01:58:29.156 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min
2006-06-10 01:58:29.158 AutoExpire: Required Free Space: 6.1 GB w/freq: 10 min
2006-06-10 01:58:31.109 Reschedule requested for id -1.
2006-06-10 01:58:34.703 Scheduled 138 items in 3.6 = 2.72 match + 0.87 place
2006-06-10 01:58:34.706 Recording starts soon, AUTO-Startup assumed
2006-06-10 01:59:02.414 MainServer::HandleAnnounce Monitor
2006-06-10 01:59:02.414 adding: twinion.xensoft.com as a client (events: 0)
2006-06-10 01:59:02.570 MainServer::HandleAnnounce Monitor
2006-06-10 01:59:02.571 adding: twinion.xensoft.com as a client (events: 1)
2006-06-10 01:59:58.229 TVRec(1): Changing from None to RecordingOnly
2006-06-10 01:59:58.565 Started recording: Good Eats "Salad Daze":
channel 1034 on cardid 1, sourceid 1
select timeout - ivtv driver has stopped responding
select timeout - ivtv driver has stopped responding
...

What should I try next? Where should I be looking?

On 6/4/06, Derek Battams <derek at battams.ca> wrote:
> Quoting John Westlund <john.westlund at gmail.com>:
>
> > I see other people having similar problems but I'm still banging my
> > head against this issue.
> >
> > Recently updated to the 0.6.2 driver and now when I try and record I
> > get something similar to:
> >
> > frontend:
> > 2006-06-03 17:45:06.028 TV: Attempting to change from None to WatchingLiveTV
> > 2006-06-03 17:45:06.034 Using protocol version 26
> > 2006-06-03 17:45:06.591
> > RingBuf(/var/storage/MythTV/1014_20060603174506.mpg): Invalid file (fd
> > 16) when opening '/var/storage/MythTV/1014_20060603174506.mpg'. 12
> > retries remaining.
> > 2006-06-03 17:45:07.094
> > RingBuf(/var/storage/MythTV/1014_20060603174506.mpg): Invalid file (fd
> > 16) when opening '/var/storage/MythTV/1014_20060603174506.mpg'. 11
> > retries remaining.
> > 2006-06-03 17:45:07.853 NVP: Couldn't find a matching decoder for:
> > /var/storage/MythTV/1014_20060603174506.mpg
> > 2006-06-03 17:45:07.858 TV Error: StartPlayer(): NVP is not playing
> > after 20000 msec
> > 2006-06-03 17:45:12.734 TV Error: LiveTV not successfully started
> >
> > backend:
> > 2006-06-03 17:45:06.076 TVRec(1): Changing from None to WatchingLiveTV
> > 2006-06-03 17:45:06.079 MainServer::HandleAnnounce Monitor
> > 2006-06-03 17:45:06.079 adding: twinion.xensoft.com as a client (events: 1)
> > 2006-06-03 17:45:07.884 TVRec(1): Changing from WatchingLiveTV to None
> > select timeout - ivtv driver has stopped responding
> > 2006-06-03 17:45:12.595 Finished recording A Haunting "The
> > Diabolical": channel 1014
> >
> > Occasionally it will continue to record but "select timeout - ivtv
> > driver has stopped responding" messages continues once every couple of
> > seconds.
> >
> > I've tried updating to the 0.7 drivers and then I get nothing out of
> > the device, and Myth gives me:
> > TV: Attempting to change from None to WatchingLiveTV
> > 2006-06-03 22:24:26.702 Using protocol version 26
> > 2006-06-03 22:24:26.980
> > RingBuf(/var/storage/MythTV/1014_20060603222426.mpg): Invalid file (fd
> > 16) when opening '/var/storage/MythTV/1014_20060603222426.mpg'. 12
> > retries remaining.
> > and eventually gives up.
> >
> > I've attempted to build the 0.6.1 driver against my
> > kernel-2.6.16-1.2122_FC5 kernel but I get the following in dmesg when
> > I try and load the modules:
> > ivtv: disagrees about version of symbol video_unregister_device
> > ivtv: Unknown symbol video_unregister_device
> > ivtv: disagrees about version of symbol video_device_alloc
> > ivtv: Unknown symbol video_device_alloc
> > ivtv: disagrees about version of symbol video_register_device
> > ivtv: Unknown symbol video_register_device
> > ivtv: disagrees about version of symbol video_device_release
> > ivtv: Unknown symbol video_device_release
> >
> > Any thoughts?
> >
> > Thanks.
>
> There is a fix in SVN for the select timeout error message.  The patch
> I submitted for this issue basically closes and reopens the PVR card
> when this error is encountered instead of just constantly reporting
> the error message, as you describe.  The only catch is that you'll
> lose ~5 seconds of the recording, but I figure that's much more
> preferable than a log file full of error messages and a partial
> recording.  The fix has worked for me, so hopefully you'll have the
> same luck.
>
>    - Derek
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>