On Wednesday 25 October 2006 21:17, Gerald Schepens wrote:
> I've also noticed that I get a lot of interrupts (like millions of
> interrupts) on the ivtv interrupt.
>
> 209: 23452898 IO-APIC-level ivtv0
>
> This after 10 1/2 hours of uptime. Since booting, there has been all
> of a couple of minutes of recording, and a few minutes of watching
> TV. Is this normal?
Yes, this is normal for a PVR350.
Regarding the CPU usage: 50% seems way too high. Can you check which
process(es) take so much CPU power? (top -d1)
I do know that processing VBI (teletext, closed captions, etc) takes a
fair bit of processing power. So make sure it is disabled in MythTV.
There have been no changes relevant to this between ivtv-0.7 and
ivtv-0.8, so my guess is that VBI is now turned on in MythTV, while it
was turned off before.
Hans
>
> Could this be an issue with buffers? Can anyone else suggest some
> other debugging info or something else I can look at?
>
> This is what my /var/log/messages ivtv initialisation looks like.
> (There are some non-related messages interlaced in with it. I left
> these in, in case they are significant.)
>
> Oct 25 02:29:13 www kernel: ivtv: no version for "struct_module"
> found: kernel tainted.
> Oct 25 02:29:13 www kernel: ivtv: ==================== START INIT
> IVTV ====================
> Oct 25 02:29:13 www kernel: ivtv: version 0.8.0 (tagged release)
> loading Oct 25 02:29:13 www kernel: ivtv: Linux version:
> 2.6.18-1.2200.fc5 mod_unload 686 REGPARM 4KSTACKS gcc-4.1
> Oct 25 02:29:13 www kernel: ivtv: In case of problems please include
> the debug info between
> Oct 25 02:29:13 www kernel: ivtv: the START INIT IVTV and END INIT
> IVTV lines, along with
> Oct 25 02:29:13 www kernel: ivtv: any module options, when mailing
> the ivtv-users mailinglist.
> Oct 25 02:29:13 www kernel: AC'97 0 analog subsections not ready
> Oct 25 02:29:13 www kernel: intel8x0_measure_ac97_clock: measured
> 55805 usecs
> Oct 25 02:29:13 www kernel: intel8x0: clocking to 48000
> Oct 25 02:29:13 www kernel: b44.c:v1.01 (Jun 16, 2006)
> Oct 25 02:29:13 www kernel: PCI: Enabling device 0000:02:05.0 (0004
> -> 0006) Oct 25 02:29:13 www kernel: ACPI: PCI Interrupt
> 0000:02:05.0[A] -> GSI 20 (level, low) -> IRQ 201
> Oct 25 02:29:13 www kernel: eth0: Broadcom 4400 10/100BaseT Ethernet
> 00:e0:18:f9:c2:be
> Oct 25 02:29:13 www kernel: ivtv0: Autodetected Hauppauge WinTV
> PVR-350 card (cx23415 based)
> Oct 25 02:29:13 www kernel: PCI: Enabling device 0000:02:0d.0 (0014
> -> 0016) Oct 25 02:29:13 www kernel: ACPI: PCI Interrupt
> 0000:02:0d.0[A] -> GSI 21 (level, low) -> IRQ 209
> Oct 25 02:29:13 www kernel: ivtv0: Unreasonably low latency timer,
> setting to 64 (was 32)
> Oct 25 02:29:13 www kernel: sd 0:0:0:0: Attached scsi generic sg0
> type 0 Oct 25 02:29:13 www kernel: sd 1:0:0:0: Attached scsi generic
> sg1 type 0 Oct 25 02:29:13 www kernel: Floppy drive(s): fd0 is 1.44M
> Oct 25 02:29:13 www kernel: FDC 0 is a post-1991 82077
> Oct 25 02:29:13 www kernel: nvidia: module license 'NVIDIA' taints
> kernel. Oct 25 02:29:13 www kernel: USB Universal Host Controller
> Interface driver v3.0
> Oct 25 02:29:13 www kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware
> (262144 bytes)
> Oct 25 02:29:13 www kernel: ivtv0: loaded v4l-cx2341x-dec.fw firmware
> (262144 bytes)
> Oct 25 02:29:13 www kernel: tveeprom 0-0050: Hauppauge model 48132,
> rev J323, serial# 6813931
> Oct 25 02:29:13 www kernel: tveeprom 0-0050: tuner model is Philips
> FM1236 (idx 23, type 2)
> Oct 25 02:29:13 www kernel: tveeprom 0-0050: TV standards NTSC(M)
> (eeprom 0x08)
> Oct 25 02:29:13 www kernel: tveeprom 0-0050: audio processor is
> MSP4448 (idx 27)
> Oct 25 02:29:13 www kernel: tveeprom 0-0050: decoder processor is
> SAA7115 (idx 19)
> Oct 25 02:29:13 www kernel: tveeprom 0-0050: has radio, has IR remote
> Oct 25 02:29:13 www kernel: tuner 0-0061: chip found @ 0xc2 (ivtv i2c
> driver #0)
> Oct 25 02:29:13 www kernel: saa7115 0-0021: saa7115 found @ 0x42
> (ivtv i2c driver #0)
> Oct 25 02:29:13 www kernel: saa7127 0-0044: saa7127 found @ 0x88
> (ivtv i2c driver #0)
> Oct 25 02:29:13 www kernel: msp3400 0-0040: MSP4448G-A2 found @ 0x80
> (ivtv i2c driver #0)
> Oct 25 02:29:13 www kernel: msp3400 0-0040: MSP4448G-A2 supports
> radio, mode is autodetect and autoselect
> Oct 25 02:29:13 www kernel: ivtv0: Encoder revision: 0x02050032
> Oct 25 02:29:13 www kernel: ivtv0: Decoder revision: 0x02020023
> Oct 25 02:29:13 www kernel: ivtv0: Registered device video0 for
> encoder MPEG Oct 25 02:29:13 www kernel: ivtv0: Registered device
> video32 for encoder YUV Oct 25 02:29:13 www kernel: ivtv0: Registered
> device vbi0 for encoder VBI Oct 25 02:29:13 www kernel: ivtv0:
> Registered device video24 for encoder PCM audio
> Oct 25 02:29:13 www kernel: ivtv0: Registered device radio0 for
> encoder radio
> Oct 25 02:29:13 www kernel: ivtv0: Registered device video16 for
> decoder MPEG
> Oct 25 02:29:13 www kernel: ivtv0: Registered device vbi8 for decoder
> VBI Oct 25 02:29:13 www kernel: ivtv0: Registered device vbi16 for
> decoder VOUT Oct 25 02:29:13 www kernel: ivtv0: Registered device
> video48 for decoder YUV Oct 25 02:29:13 www kernel: ivtv0: loaded
> v4l-cx2341x-init.mpg firmware (155648 bytes)
> Oct 25 02:29:13 www kernel: tuner 0-0061: type set to 2 (Philips NTSC
> (FI1236,FM1236 and compatibles))
> Oct 25 02:29:13 www kernel: ivtv0: Initialized Hauppauge WinTV
> PVR-350, card #0
> Oct 25 02:29:13 www kernel: ivtv: ==================== END INIT IVTV
> ====================
> Oct 25 02:29:13 www kernel: ACPI: PCI Interrupt 0000:01:00.0[A] ->
> GSI 16 (level, low) -> IRQ 217
> Oct 25 02:29:13 www kernel: NVRM: loading NVIDIA Linux x86 Kernel
> Module 1.0-8776 Mon Oct 16 21:56:04 PDT 2006
> Oct 25 02:29:13 www kernel: ACPI: PCI Interrupt 0000:00:1d.0[A] ->
> GSI 16 (level, low) -> IRQ 217
> Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.0: UHCI Host
> Controller Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.0: new USB
> bus registered, assigned bus number 1
> Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.0: irq 217, io base
> 0x0000d800
> Oct 25 02:29:13 www kernel: usb usb1: configuration #1 chosen from 1
> choice Oct 25 02:29:13 www kernel: hub 1-0:1.0: USB hub found
> Oct 25 02:29:13 www kernel: hub 1-0:1.0: 2 ports detected
> Oct 25 02:29:13 www kernel: ivtv0-osd: Framebuffer module loaded
> (attached to ivtv card id 0)
> Oct 25 02:29:13 www kernel: ivtv0-osd: screen coords: [0 0] -> [720
> 480] Oct 25 02:29:13 www kernel: ivtv0-osd: original global alpha =
> 208 Oct 25 02:29:13 www kernel: ivtv0-osd: current OSD state = 39 Oct
> 25 02:29:13 www kernel: ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19
> (level, low) -> IRQ 225
> Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.1: UHCI Host
> Controller Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.1: new USB
> bus registered, assigned bus number 2
> Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.1: irq 225, io base
> 0x0000d400
> Oct 25 02:29:13 www kernel: usb usb2: configuration #1 chosen from 1
> choice Oct 25 02:29:13 www kernel: hub 2-0:1.0: USB hub found
> Oct 25 02:29:13 www kernel: hub 2-0:1.0: 2 ports detected
> Oct 25 02:29:13 www kernel: ivtv0-osd: new global alpha = 208 (1 255
> 0) Oct 25 02:29:13 www kernel: ivtv0-osd: framebuffer at 0xe9510000,
> mapped to 0xf9e10000, size 1665k
> Oct 25 02:29:13 www kernel: ivtv0-osd: mode is 720x480x32,
> linelength=2880 Oct 25 02:29:13 www kernel: ACPI: PCI Interrupt
> 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 177
> Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.2: UHCI Host
> Controller Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.2: new USB
> bus registered, assigned bus number 3
> Oct 25 02:29:13 www kernel: uhci_hcd 0000:00:1d.2: irq 177, io base
> 0x0000d000
> Oct 25 02:29:13 www kernel: usb usb3: configuration #1 chosen from 1
> choice Oct 25 02:29:13 www kernel: hub 3-0:1.0: USB hub found
> Oct 25 02:29:13 www kernel: hub 3-0:1.0: 2 ports detected
> Oct 25 02:29:13 www kernel: ivtv0-osd: fb1: cx23415 TV out frame
> buffer device
> Oct 25 02:29:13 www kernel: PCI: Enabling device 0000:00:1d.7 (0004
> -> 0006)
>
> Gerald Schepens wrote:
> > I should add that this is on MythTV 0.20-142.
> >
> > David Arendt wrote:
> >> I also noticed that I have 50% CPU usage on playback through
> >> PVR-350 with ivtv 0.8.0 but as I didn't a look at the CPU usage
> >> with older versions, I can't tell if it was lower there.
> >>
> >> Gerald Schepens wrote:
> >>> I have 50% usage of my CPU when I play back video on my PVR-350
> >>> through its TV-OUT. I have never had an issue with this before.
> >>> My CPU is a 2.5 GHz Pentium 4. The CPU usage is sys usage, which
> >>> is why I think something about the ivtv, or the new kernel, is a
> >>> bit off. Everything works as it should, it just uses half the
> >>> CPU to do it!
> >>>
> >>> I am running Mythtv on Fedora Core 5 with the following packages:
> >>>
> >>> PVR-350, using hardware decoder / TV-OUT
> >>> ivtv-0.8.0-121.fc5.at
> >>> ivtv-firmware-1.8a-10.at
> >>> ivtv-kmdl-2.6.18-1.2200.fc5-0.8.0-121.fc5.at
> >>> ivtv_xdriver-0.10.6-6.fc5.at
> >>>
> >>> And kernel 2.6.18-1.2200.fc5.
> >>>
> >>> With the previous kernel (2.6.17-1.2187_FC5) and the ivtv version
> >>> (whichever one goes with the previous kernel and 2.6.17), the CPU
> >>> usage was negligible.
> >>>
> >>>
> >>> Is anyone else having this issue? Is there a configuration
> >>> tweak, or is it an issue with the code?
> >>>
> >>> Thanks,
> >>>
> >>> Gerald Schepens
> >>>
> >>> _______________________________________________
> >>> ivtv-users mailing list
> >>> [email protected]
> >>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >>
> >> _______________________________________________
> >> ivtv-users mailing list
> >> [email protected]
> >> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
