Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: users

mythtv box freezes when recording with ivtv 0.10.1, question about 0.10.5

 

 

ivtv users RSS feed   Index | Next | Previous | View Threaded


wfaris at gmail

Sep 14, 2007, 6:17 PM

Post #1 of 2 (411 views)
Permalink
mythtv box freezes when recording with ivtv 0.10.1, question about 0.10.5

I have a box that was running mythtv with no problems month after month
(awesome). I recently wiped the box and installed mythbuntu (had been using
FC prior to recent problems) and the box frequently freezes now, it will not
stay up more than a day. I have been trying to isolate the problem and I
have learned that freezes only occur when tv is being recorded. I had
originally thought the problem was elsewhere (video driver problem) but
after some tests this week I have convinced myself that the freeze only
occurs while tv is being recorded, (but not all the time, sometimes I can
record multiple 30 and 60 minute programs a-ok). Because of this I have
been looking around the ivtv wiki (i have a 350 and a 250 installed) and I
noticed this recent change in the 0.10.x (release)

http://ivtvdriver.org/trac/changeset/3951

Was wondering what the symptoms of the problem fixed in that change set
would be. I don't understand the diff at all but when I read
the comment in the change log " Fix lockup when capturing vbi and PCM at the
same time." I thought maybe this was my problem. I am running 0.10.1 ivtv
right now. While reading stuff on the wiki it seems that there has been
alot of code refactoring in 0.10.x, would it be safer to run an earlier
version of the driver? I wish I had noted the version of ivtv I was using
in previous incarnation of this box as it worked like a charm, but of course
i did not, plus the wiki mentions the place to be for support is 0.10.x .
If anyone knowledgeable about ivtv could explain what the symptoms
0.10.5fixed I would really appreciate it. I would rather not get
0.10.5 unless there is reason to think it may fix the problem.

I have a PVR 350 and a PVR 250 installed. The ivtv info from dmesg is
below. My watcher scripts have seen the crash occur when

A) 350 is recording and 250 is not
B) 250 is recording and 350 is not
C) when both 350 and 250 are recording

If I disable all recordings the box stays healthy for +72 hours (never seen
it go down). If I enable recording it will typically not stay up more than
12 hours, every freeze this week happened when 1 or 2 programs were being
recorded.

Is there a way to get ivtv driver itself to log debug level info to narrow
things down at all?

If your still reading this message thanks.

wfaris [at] myt:~$ uname -a
Linux myth 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
GNU/Linux


[ 20.609573] ivtv: ==================== START INIT IVTV
====================
[ 20.609579] ivtv: version 0.10.1 (tagged release) loading
[ 20.609582] ivtv: Linux version: 2.6.20-16-generic SMP mod_unload 586
[ 20.609586] ivtv: In case of problems please include the debug info
between
[ 20.609589] ivtv: the START INIT IVTV and END INIT IVTV lines, along
with
[ 20.609593] ivtv: any module options, when mailing the ivtv-users
mailinglist.
[ 20.609707] ivtv0: Autodetected Hauppauge card (cx23415 based)
[ 20.609808] ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) ->
IRQ 22
[ 20.609828] ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
[ 20.681937] Linux agpgart interface v0.102 (c) Dave Jones
[ 20.707887] parport: PnPBIOS parport detected.
[ 20.707965] parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[PCSPP,TRISTATE,COMPAT,ECP,DMA]
[ 20.818251] lirc_dev: lirc_register_plugin: sample_rate: 0
[ 20.818533] lirc_atiusb[3]: on usb1:3
[ 20.818568] usbcore: registered new interface driver lirc_atiusb
[ 20.870543] nvidia: module license 'NVIDIA' taints kernel.
[ 21.454540] NET: Registered protocol family 10
[ 21.454653] lo: Disabled Privacy Extensions
[ 21.626157] ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[ 21.691257] ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
[ 21.912216] ivtv0: Encoder revision: 0x02060039
[ 21.920216] ivtv0: Decoder revision: 0x02020023
[ 21.987507] tveeprom 0-0050: Hauppauge model 48132, rev K268, serial#
8289759
[ 21.987512] tveeprom 0-0050: tuner model is LG TAPE H001F MK3 (idx 68,
type 47)
[ 21.987515] tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
[ 21.987518] tveeprom 0-0050: audio processor is MSP4448 (idx 27)
[ 21.987521] tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
[ 21.987523] tveeprom 0-0050: has radio, has IR receiver, has no IR
transmitter
[ 21.987527] ivtv0: Autodetected Hauppauge WinTV PVR-350
[ 22.017873] tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
[ 22.017909] tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
[ 22.022539] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 22.094333] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv
i2c driver #0)
[ 22.334158] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
[ 22.361882] msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
[ 22.361886] msp3400 0-0040: MSP4448G-A2 supports radio, mode is
autodetect and autoselect
[ 22.362230] ivtv0: Registered device video0 for encoder MPEG (4 MB)
[ 22.362440] ivtv0: Registered device video32 for encoder YUV (2 MB)
[ 22.362686] ivtv0: Registered device vbi0 for encoder VBI (1 MB)
[ 22.362789] ivtv0: Registered device video24 for encoder PCM audio (1 MB)
[ 22.363054] ivtv0: Registered device radio0 for encoder radio
[ 22.363086] ivtv0: Registered device video16 for decoder MPEG (1 MB)
[ 22.363150] ivtv0: Registered device vbi8 for decoder VBI (1 MB)
[ 22.363594] ivtv0: Registered device vbi16 for decoder VOUT
[ 22.363623] ivtv0: Registered device video48 for decoder YUV (1 MB)
[ 22.419793] ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
[ 22.526812] tuner 0-0061: type set to 47 (LG NTSC (TAPE series))
[ 22.899129] ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
[ 22.899199] ivtv: ====================== NEXT CARD
======================
[ 22.899205] ivtv1: Autodetected Hauppauge card (cx23415 based)
[ 22.899309] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) ->
IRQ 23
[ 22.899325] ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
[ 23.527393] ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[ 23.537946] ivtv1: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
[ 23.621066] APIC error on CPU0: 00(40)
[ 23.759856] ivtv1: Encoder revision: 0x02060039
[ 23.767844] ivtv1: Decoder revision: 0x02020023
[ 23.775963] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
[ 23.831565] saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv
i2c driver #1)
[ 24.024448] msp3400 1-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #1)
[ 24.024451] msp3400 1-0040: MSP3445G-B8 supports radio, mode is
autodetect and autoselect
[ 24.092600] tveeprom 1-0050: Hauppauge model 48012, rev G326, serial#
2603522
[ 24.092605] tveeprom 1-0050: tuner model is Temic 4036FY5 (idx 26, type
8)
[ 24.092609] tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
[ 24.092612] tveeprom 1-0050: audio processor is MSP3445 (idx 12)
[ 24.092614] tveeprom 1-0050: has radio
[ 24.092617] ivtv1: Autodetected Hauppauge WinTV PVR-250
[ 24.112295] ivtv1: Registered device video1 for encoder MPEG (4 MB)
[ 24.112621] ivtv1: Registered device video33 for encoder YUV (2 MB)
[ 24.112973] ivtv1: Registered device vbi1 for encoder VBI (1 MB)
[ 24.113188] ivtv1: Registered device video25 for encoder PCM audio (1 MB)
[ 24.113567] ivtv1: Registered device radio1 for encoder radio
[ 24.113587] tuner 1-0061: type set to 8 (Temic NTSC (4036 FY5))
[ 24.492629] ivtv1: Initialized Hauppauge WinTV PVR-250, card #1
[ 24.492654] ivtv: ==================== END INIT IVTV
====================


wepprop at sbcglobal

Sep 15, 2007, 6:59 AM

Post #2 of 2 (377 views)
Permalink
Re: mythtv box freezes when recording with ivtv 0.10.1, question about 0.10.5 [In reply to]

William Damian Faris wrote:
> I have a box that was running mythtv with no problems month after
> month (awesome). I recently wiped the box and installed mythbuntu
> (had been using FC prior to recent problems) and the box frequently
> freezes now, it will not stay up more than a day. I have been trying
> to isolate the problem and I have learned that freezes only occur when
> tv is being recorded. I had originally thought the problem was
> elsewhere (video driver problem) but after some tests this week I have
> convinced myself that the freeze only occurs while tv is being
> recorded, (but not all the time, sometimes I can record multiple 30
> and 60 minute programs a-ok). Because of this I have been looking
> around the ivtv wiki (i have a 350 and a 250 installed) and I noticed
> this recent change in the 0.10.x (release)
>
> http://ivtvdriver.org/trac/changeset/3951
>
> Was wondering what the symptoms of the problem fixed in that change
> set would be. I don't understand the diff at all but when I read
> the comment in the change log " Fix lockup when capturing vbi and PCM
> at the same time." I thought maybe this was my problem. I am running
> 0.10.1 ivtv right now. While reading stuff on the wiki it seems
> that there has been alot of code refactoring in 0.10.x, would it be
> safer to run an earlier version of the driver? I wish I had noted the
> version of ivtv I was using in previous incarnation of this box as it
> worked like a charm, but of course i did not, plus the wiki mentions
> the place to be for support is 0.10.x . If anyone knowledgeable
> about ivtv could explain what the symptoms 0.10.5 fixed I would really
> appreciate it. I would rather not get 0.10.5 unless there is reason
> to think it may fix the problem.
>
> I have a PVR 350 and a PVR 250 installed. The ivtv info from dmesg is
> below. My watcher scripts have seen the crash occur when
>
> A) 350 is recording and 250 is not
> B) 250 is recording and 350 is not
> C) when both 350 and 250 are recording
>
> If I disable all recordings the box stays healthy for +72 hours (never
> seen it go down). If I enable recording it will typically not stay up
> more than 12 hours, every freeze this week happened when 1 or 2
> programs were being recorded.
>
> Is there a way to get ivtv driver itself to log debug level info to
> narrow things down at all?
>
> If your still reading this message thanks.
Your problem sounds similar to a problem I was having until recently,
but I can't be certain they are the same. My problem was lockups that
occurred only at the start of a recording.while your appear to occur
during a recording, if I read your description correctly? Regardless,
my problem was *not* fixed in 0.10.5 but it was fixed a later
developmental shapshot and that's what I'm running now. My current
uptime is at 54 days and counting with many hundreds of recordings made,
so I think my problem is fixed in the current trunk. Perhaps yours
might be as well. More description in the following threads:

http://www.gossamer-threads.com/lists/ivtv/users/36044
http://www.gossamer-threads.com/lists/ivtv/users/36274
http://www.gossamer-threads.com/lists/ivtv/users/36293

Bill

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

ivtv users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.