On Jan 26, 2007, at 5:31 AM, Martin van Es wrote:

> Hi,
>
> I've recently upgraded my pvr-150 to a pvr-500 and am seeing
> occasional (+/- 5 minutes) mpg artefacts (glitches) in the
> recorded/shown mpg stream (mythtv). I started out with kernel 2.6.16 /
> ivtv 0.6.6, but it turned out the new Samsung tuner wasn't recognized
> so I upgraded to 2.6.19 / ivtv 0.9.1. This works fine (I can watch TV
> now) except for the fact that I now have the forementioned occasional
> glitches/artefacts in the lower part of my screen.

I get these too. They are unrelated to signal quality or hard drive  
activity as far as I can tell. And they happen frequently.

My setup is a SMP PPC machine with ivtv-0.9.1 and a PVR-350. I'm not  
sure what kind of processor architecture you're running, but it would  
be interesting to hear if you are using a x86, PPC, etc and the  
endianness of it.

The only way to change a card's interrupt/IRQ is to physically move  
it from one PCI slot to another.

- Rick

> Things I tried so far to resolve this:
> 1. Read the archives of this mailinglist (both dev/users). I could
> find only one reference to glitches and they were in the output of
> pvr-350.
> 2. change latencies on both pvr-500 pci device ids (40 to 80)
> 3. compile and use ivtv-svn (see dmesg output).
> 4. mythtv asyncdb.patch, which didn't succesfully compile.
> 5. use most recent pvr-500 firmware
> 6. switch off aggressive and extra audiobuffering
> 7. tried changing interrupts of the ivtv devices to prevent interrupt
> sharing, but couldn't find a way to do this.
>
> I also tried to set different (ivtv) debug levels to see if I could
> discriminate certain messages after the error, but the dmesg output
> was either too abundant (irq, dma, ioctl) or didn't show anything
> after a glitch (warn, info etc).
>
> I am able to reproduce the problem using 'cat /dev/video1 > test.mpg'
> so mythtv is out of the equasion.
>
> My questions to the audience are:
> 1. Is there anything I missed worth trying, or do people know how to
> do things I couldn't? (rearrange interrupts eg)
> 2. Is my pvr-500 broken?
>
> I'll attach a pic to illustrate the problem.
>
>
> Grtz.
> Martin van Es
>
> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.9.2 (development revision 3716) loading
> ivtv:  Linux version: 2.6.19 mod_unload CYRIXIII REGPARM
> 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 card (cx23416 based)
> ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKB] -> GSI 12 (level,
> low) -> IRQ 12
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
> tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tuner 1-0060: TEA5767 detected.
> tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> tuner 1-0060: type set to 62 (Philips TEA5767HN FM Radio)
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> tveeprom 1-0050: Hauppauge model 23559, rev D596, serial# 9822801
> tveeprom 1-0050: tuner model is Samsung TCPG 6121P30A (idx 96, type  
> 73)
> tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
> (eeprom 0x74)
> tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx
> 101, type 62)
> tveeprom 1-0050: audio processor is CX25843 (idx 37)
> tveeprom 1-0050: decoder processor is CX25843 (idx 30)
> tveeprom 1-0050: has radio, has no IR remote
> ivtv0: Autodetected WinTV PVR 500 (unit #1)
> ivtv0: Encoder revision: 0x02060039
> ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011,
> 0x02040024 or 0x02050032.
> ivtv0: Registered device video0 for encoder MPEG
> ivtv0: Registered device video32 for encoder YUV
> ivtv0: Registered device vbi0 for encoder VBI
> ivtv0: Registered device video24 for encoder PCM audio
> ivtv0: Registered device radio0 for encoder radio
> tuner 1-0061: type set to 73 (Samsung TCPG 6121P30A)
> ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
> ivtv:  ======================  NEXT CARD  ======================
> ivtv1: Autodetected Hauppauge card (cx23416 based)
> ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKC] -> GSI 10 (level,
> low) -> IRQ 10
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
> tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
> cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
> tveeprom 2-0050: Hauppauge model 23559, rev D596, serial# 9822801
> tveeprom 2-0050: tuner model is Samsung TCPG 6121P30A (idx 96, type  
> 73)
> tveeprom 2-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K)
> (eeprom 0x74)
> tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio (idx
> 101, type 62)
> tveeprom 2-0050: audio processor is CX25843 (idx 37)
> tveeprom 2-0050: decoder processor is CX25843 (idx 30)
> tveeprom 2-0050: has radio, has no IR remote
> ivtv1: Correcting tveeprom data: no radio present on second unit
> ivtv1: Autodetected WinTV PVR 500 (unit #2)
> ivtv1: Encoder revision: 0x02060039
> ivtv1 warning: Encoder Firmware can be buggy, use version 0x02040011,
> 0x02040024 or 0x02050032.
> ivtv1: Registered device video1 for encoder MPEG
> ivtv1: Registered device video33 for encoder YUV
> ivtv1: Registered device vbi1 for encoder VBI
> ivtv1: Registered device video25 for encoder PCM audio
> tuner 2-0061: type set to 73 (Samsung TCPG 6121P30A)
> ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
> ivtv:  ====================  END INIT IVTV  ====================
>
> lspci:
> 00:00.0 Host bridge: VIA Technologies, Inc. VT8623 [Apollo CLE266]
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
> 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 80)
> 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 80)
> 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 80)
> 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
> 00:11.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> 00:11.5 Multimedia audio controller: VIA Technologies, Inc.
> VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine- 
> II] (rev 74)
> 00:14.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge
> (non-transparent mode) (rev 11)
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623
> [Apollo CLE266] integrated CastleRock graphics (rev 03)
> 02:08.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> 02:09.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
>
> /proc/interrupts
>           CPU0
>  0:   87569287    XT-PIC-XT        timer
>  1:          2    XT-PIC-XT        i8042
>  2:          0    XT-PIC-XT        cascade
>  8:          1    XT-PIC-XT        rtc
>  9:          0    XT-PIC-XT        acpi
> 10:    1792940    XT-PIC-XT        ehci_hcd:usb1, uhci_hcd:usb4,  
> VIA8233, ivtv1
> 11:    7889976    XT-PIC-XT        uhci_hcd:usb2, eth0, [EMAIL PROTECTED]: 
> 0000:01:00.0
> 12:     427243    XT-PIC-XT        uhci_hcd:usb3, ivtv0
> 14:     554557    XT-PIC-XT        ide0
> 15:         52    XT-PIC-XT        ide1
> NMI:          0
> ERR:          0
>
> /proc/dma
> 4: cascade
> <glitches.jpg>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel


_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Reply via email to