I tried 0.4.4 from CVS and had the following problem: vdr starts with an analog channel (pvrinput-plugin), picture + sound is o.k.
I switch to another channel and a black picture with no sound appears. It is not possible to get picture back until I make a reboot. The log shows no errors. This problem must be caused by changes made in the last days. It is not the tinny audio patch - I already tried an older version of cx25840-audio.c without success. With ivtv from trunk (build with v4l-dvb mercurial) the channel switch problem does not exist! But unfortunately again a firmware timeout appeared after zapping a few minutes through the channels. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: Friday, April 21, 2006 12:00 PM > To: [email protected] > Subject: ivtv-devel Digest, Vol 8, Issue 29 > > > Send ivtv-devel mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ivtv-devel digest..." > > > Today's Topics: > > 1. ivtv too slow in xen0 kernel (Sietse Visser) > 2. Fwd: ivtv too slow in xen0 kernel (Sietse Visser) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 20 Apr 2006 20:56:10 +0200 > From: "Sietse Visser" <[EMAIL PROTECTED]> > Subject: [ivtv-devel] ivtv too slow in xen0 kernel > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > I am trying to use ivtv in a xen0 kernel (FC5 with ATRPM ivtv modules). > It works, but the system can't keep up - mplayer /dev/video0 is stuttery, > and CPU goes to 100% for one or two seconds, and then continues playing. > > The following line in /var/log/messages might have to do with it: > > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 32768 > bytes at device 0000:00:06.0 > > Any ideas on how to resolve this? > > Regards, > Sietse > > Apr 20 20:33:26 prefect kernel: ivtv: ==================== START > INIT IVTV > ==================== > Apr 20 20:33:26 prefect kernel: ivtv: version 0.6.1 (development snapshot > compiled on Wed Mar 29 17:13:19 2006) loading > Apr 20 20:33:26 prefect kernel: ivtv: Linux version: > 2.6.16-1.2080_FC5xen0SMP 686 > gcc-4.1 > Apr 20 20:33:26 prefect kernel: ivtv: In case of problems please include > the debug info between > Apr 20 20:33:26 prefect kernel: ivtv: the START INIT IVTV and > END INIT IVTV > lines, along with > Apr 20 20:33:26 prefect kernel: ivtv: any module options, when > mailing the > ivtv-users mailinglist. > Apr 20 20:33:26 prefect kernel: ivtv0: Autodetected Hauppauge > WinTV PVR-250 > card (cx23416 based) > Apr 20 20:33:26 prefect kernel: ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI > 17 (level, low) -> IRQ 17 > Apr 20 20:33:26 prefect kernel: ivtv0: Unreasonably low latency timer, > setting to 64 (was 32) > Apr 20 20:33:26 prefect kernel: tveeprom 1-0050: Hauppauge model > 32054, rev > B148, serial# 2767120 > Apr 20 20:33:26 prefect kernel: tveeprom 1-0050: tuner model is LG > TP18PSB11D (idx 48, type 29) > Apr 20 20:33:26 prefect kernel: tveeprom 1-0050: TV standards PAL(B/G) > (eeprom 0x04) > Apr 20 20:33:26 prefect kernel: tveeprom 1-0050: audio processor > is MSP4418 > (idx 25) > Apr 20 20:33:26 prefect kernel: tveeprom 1-0050: decoder processor is > SAA7115 (idx 19) > Apr 20 20:33:26 prefect kernel: tveeprom 1-0050: has no radio, > has IR remote > Apr 20 20:33:26 prefect kernel: tuner 1-0061: chip found @ 0xc2 (ivtv i2c > driver #0) > Apr 20 20:33:26 prefect kernel: saa7115 1-0021: saa7115 found @ 0x42 (ivtv > i2c driver #0) > Apr 20 20:33:26 prefect kernel: msp3400 1-0040: MSP4418G-A2 found @ 0x80 > (ivtv i2c driver #0) > Apr 20 20:33:26 prefect kernel: msp3400 1-0040: MSP4418G-A2 supports nicam > and radio, mode is autodetect and autoselect > Apr 20 20:33:26 prefect kernel: nvidia: module license 'NVIDIA' taints > kernel. > Apr 20 20:33:26 prefect kernel: USB Universal Host Controller Interface > driver v2.3 > Apr 20 20:33:26 prefect kernel: sd 0:0:0:0: Attached scsi generic > sg0 type 0 > Apr 20 20:33:26 prefect kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware > (262144 bytes) > Apr 20 20:33:26 prefect kernel: ivtv0: Encoder revision: 0x02040024 > Apr 20 20:33:26 prefect kernel: ivtv0: Allocate DMA encoder MPEG > stream: 128 > x 32768 buffers (4096KB total) > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 32768 > bytes at device 0000:00:06.0 > Apr 20 20:33:26 prefect last message repeated 63 times > Apr 20 20:33:26 prefect kernel: ivtv0: Allocate DMA encoder YUV > stream: 161 > x 12960 buffers (2048KB total) > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 12960 > bytes at device 0000:00:06.0 > Apr 20 20:33:26 prefect last message repeated 160 times > Apr 20 20:33:26 prefect kernel: ivtv0: Allocate DMA encoder VBI > stream: 80 x > 26208 buffers (2048KB total) > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 26208 > bytes at device 0000:00:06.0 > Apr 20 20:33:26 prefect last message repeated 79 times > Apr 20 20:33:26 prefect kernel: ivtv0: Allocate DMA encoder PCM audio > stream: 455 x 4608 buffers (2048KB total) > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 5460 > bytes at device 0000:00:06.0 > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 4608 > bytes at device 0000:00:06.0 > Apr 20 20:33:26 prefect last message repeated 454 times > Apr 20 20:33:26 prefect kernel: tuner 1-0061: type set to 29 (LG PAL_BG > (TPI8PSB11D)) > Apr 20 20:33:26 prefect kernel: ivtv0: Initialized Hauppauge > WinTV PVR-250, > card #0 > Apr 20 20:33:26 prefect kernel: ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI > 22 (level, low) -> IRQ 19 > Apr 20 20:33:26 prefect kernel: PCI: Via IRQ fixup for > 0000:00:11.5, from 12 > to 3 > Apr 20 20:33:26 prefect kernel: ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI > 18 (level, low) -> IRQ 20 > Apr 20 20:33:26 prefect kernel: ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI > 21 (level, low) -> IRQ 21 > Apr 20 20:33:26 prefect kernel: PCI: Via IRQ fixup for > 0000:00:10.4, from 12 > to 5 > Apr 20 20:33:26 prefect kernel: ehci_hcd 0000:00:10.4: EHCI Host > Controller > Apr 20 20:33:26 prefect kernel: ehci_hcd 0000:00:10.4: new USB bus > registered, assigned bus number 1 > Apr 20 20:33:26 prefect kernel: ehci_hcd 0000:00:10.4: irq 21, io mem > 0xcfffed00 > Apr 20 20:33:26 prefect kernel: ehci_hcd 0000:00:10.4: USB 2.0 > started, EHCI > 1.00, driver 10 Dec 2004 > Apr 20 20:33:26 prefect kernel: usb usb1: configuration #1 chosen from 1 > choice > Apr 20 20:33:26 prefect kernel: hub 1-0:1.0: USB hub found > Apr 20 20:33:26 prefect kernel: hub 1-0:1.0: 8 ports detected > Apr 20 20:33:26 prefect kernel: ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI > 21 (level, low) -> IRQ 21 > Apr 20 20:33:26 prefect kernel: PCI: Via IRQ fixup for > 0000:00:10.0, from 11 > to 5 > Apr 20 20:33:26 prefect kernel: uhci_hcd 0000:00:10.0: UHCI Host > Controller > Apr 20 20:33:26 prefect kernel: uhci_hcd 0000:00:10.0: new USB bus > registered, assigned bus number 2 > Apr 20 20:33:26 prefect kernel: uhci_hcd 0000:00:10.0: irq 21, io base > 0x0000ac00 > Apr 20 20:33:26 prefect kernel: usb usb2: configuration #1 chosen from 1 > choice > Apr 20 20:33:27 prefect kernel: hub 2-0:1.0: USB hub found > Apr 20 20:33:27 prefect kernel: hub 2-0:1.0: 2 ports detected > Apr 20 20:33:27 prefect kernel: ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI > 21 (level, low) -> IRQ 21 > Apr 20 20:33:27 prefect kernel: PCI: Via IRQ fixup for > 0000:00:10.1, from 11 > to 5 > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.1: UHCI Host > Controller > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.1: new USB bus > registered, assigned bus number 3 > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.1: irq 21, io base > 0x0000b000 > Apr 20 20:33:27 prefect kernel: usb usb3: configuration #1 chosen from 1 > choice > Apr 20 20:33:27 prefect kernel: hub 3-0:1.0: USB hub found > Apr 20 20:33:27 prefect kernel: hub 3-0:1.0: 2 ports detected > Apr 20 20:33:27 prefect kernel: ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI > 21 (level, low) -> IRQ 21 > Apr 20 20:33:27 prefect kernel: PCI: Via IRQ fixup for > 0000:00:10.2, from 10 > to 5 > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.2: UHCI Host > Controller > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.2: new USB bus > registered, assigned bus number 4 > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.2: irq 21, io base > 0x0000b400 > Apr 20 20:33:27 prefect kernel: usb usb4: configuration #1 chosen from 1 > choice > Apr 20 20:33:27 prefect kernel: hub 4-0:1.0: USB hub found > Apr 20 20:33:27 prefect kernel: hub 4-0:1.0: 2 ports detected > Apr 20 20:33:27 prefect kernel: ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI > 21 (level, low) -> IRQ 21 > Apr 20 20:33:27 prefect kernel: PCI: Via IRQ fixup for > 0000:00:10.3, from 10 > to 5 > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.3: UHCI Host > Controller > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.3: new USB bus > registered, assigned bus number 5 > Apr 20 20:33:27 prefect kernel: uhci_hcd 0000:00:10.3: irq 21, io base > 0x0000b800 > Apr 20 20:33:27 prefect kernel: usb usb5: configuration #1 chosen from 1 > choice > Apr 20 20:33:27 prefect kernel: hub 5-0:1.0: USB hub found > Apr 20 20:33:27 prefect kernel: hub 5-0:1.0: 2 ports detected > Apr 20 20:33:27 prefect kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI > 16 (level, low) -> IRQ 18 > Apr 20 20:33:27 prefect kernel: NVRM: loading NVIDIA Linux x86 Kernel > Module 1.0-8756 Wed Mar 29 14:26:26 PST 2006 > Apr 20 20:33:27 prefect kernel: ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI > 19 (level, low) -> IRQ 22 > Apr 20 20:33:27 prefect kernel: PCI: Via IRQ fixup for > 0000:00:0e.0, from 5 > to 6 > Apr 20 20:33:27 prefect kernel: ohci1394: fw-host0: OHCI-1394 1.0 (PCI): > IRQ=[22] MMIO=[cfffe000-cfffe7ff] Max Packet=[2048] IR/IT > contexts=[4/8] > Apr 20 20:33:27 prefect kernel: ivtv: ==================== END INIT IVTV > ==================== > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://ivtvdriver.org/pipermail/ivtv-devel/attachments/20060420/4d > 919a08/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Thu, 20 Apr 2006 23:30:36 +0200 > From: "Sietse Visser" <[EMAIL PROTECTED]> > Subject: [ivtv-devel] Fwd: ivtv too slow in xen0 kernel > To: "Discussion list for development of the IVTV driver" > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Apr 20 20:33:26 prefect kernel: PCI-DMA: Out of SW-IOMMU space for 32768 > bytes at device 0000:00:06.0 > > > According to the kernel source: > > static void swiotlb_full(struct device *dev, size_t size, int > dir, int do_panic) > { > /* > * Ran out of IOMMU space for this operation. This is very bad. > * Unfortunately the drivers cannot handle this operation properly. > * unless they check for pci_dma_mapping_error (most don't) > * When the mapping is small enough return a static buffer to limit > * the damage, or panic when the transfer is too big. > */ > > printk(KERN_ERR > "PCI-DMA: Out of SW-IOMMU space for %lu bytes at > device %s\n", > size, dev ? dev->bus_id : "?"); > > if (size > io_tlb_overflow && do_panic) { > if (dir == PCI_DMA_FROMDEVICE || dir == > PCI_DMA_BIDIRECTIONAL) > panic("PCI-DMA: Memory would be corrupted\n"); > if (dir == PCI_DMA_TODEVICE || dir == PCI_DMA_BIDIRECTIONAL) > panic("PCI-DMA: Random memory would be DMAed\n"); > } > } > > > Hope this is helpful. > > Sietse > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://ivtvdriver.org/pipermail/ivtv-devel/attachments/20060420/09 947b03/attachment-0001.html ------------------------------ _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel End of ivtv-devel Digest, Vol 8, Issue 29 ***************************************** _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
