Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. ivtv>
  3. users
WinTV PVR-500 stops recording after some minutes (ivtv0: DMA TIMEOUT)
ramonhofer at bluewin
May 15, 2011, 5:48 AM
Post #1 of 6 (3984 views)
Permalink
Hi list

I have a WinTV PVR 500 and the "ivtv0: DMA TIMEOUT" problem which I'm
trying to solve for several months now.
After reading through wikis, forum and mailing posts but I'm still not
sure where the problem could be. Maybe I'll have to send the card back
as it could be broken or maybe there's just a little configuration I
can't get right?

I'd really appreciate any help :-)



The machine contains of an Intel DP55KG mainboard, an Intel i3 CPU.
I don't know what information exactly is important I just copied yome
which might be interesting:


$ uname -a
Linux media-server 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011
x86_64 GNU/Linux


$ apt-cache show ivtv-utils
Package: ivtv-utils
Priority: extra
Section: contrib/x11
Installed-Size: 436
Maintainer: Debian MythTV Team
<pkg-mythtv-maintainers@lists.alioth.debian.org>
Architecture: amd64
Version: 1.4.1-1
Depends: libc6 (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1),
perl, libconfig-inifiles-perl, libvideo-ivtv-perl, libvideo-capture-v4l-perl
Recommends: perl-tk, devscripts, fakeroot, unzip
Filename: pool/contrib/i/ivtv-utils/ivtv-utils_1.4.1-1_amd64.deb
Size: 136576
MD5sum: e78d3ee01e5ab3a66cc7579616fce0cc
SHA1: 9a62af48a1d4ec7098f3fd475829c1523c2a3c04
SHA256: b04aa48ac94dd803c1e1c0e506ca4327a1b689252fb4eb8a4a10a4cd16cdb77a
Description: utilities for use with the ivtv kernel driver
The IVTV project develops a kernel driver for Linux and a driver for
X11 for hardware based on Conexant's CX23415/CX23416 codec chip such
as the Hauppauge PVR 150/250/350/500 models and other supported hardware.
Homepage: http://ivtvdriver.org
Tag: hardware::video, role::program, use::configuring


$ sudo cat /var/log/syslog | grep firmware
May 15 14:30:06 media-server kernel: [ 6.188690] ivtv 0000:07:09.0:
firmware: requesting v4l-cx2341x-enc.fw
May 15 14:30:06 media-server kernel: [ 6.188700] ivtv 0000:07:08.0:
firmware: requesting v4l-cx2341x-enc.fw
May 15 14:30:06 media-server kernel: [ 6.266737] ivtv1: Loaded
v4l-cx2341x-enc.fw firmware (376836 bytes)
May 15 14:30:06 media-server kernel: [ 6.266753] ivtv0: Loaded
v4l-cx2341x-enc.fw firmware (376836 bytes)
May 15 14:30:06 media-server kernel: [ 6.482725] cx25840 3-0044:
firmware: requesting v4l-cx25840.fw
May 15 14:30:06 media-server kernel: [ 6.482764] cx25840 1-0044:
firmware: requesting v4l-cx25840.fw
May 15 14:30:06 media-server kernel: [ 10.118326] cx25840 3-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)
May 15 14:30:06 media-server kernel: [ 10.118557] cx25840 1-0044: loaded
v4l-cx25840.fw firmware (16382 bytes)


$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller
(rev 18)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16
Root Port (rev 18)
00:19.0 Ethernet controller: Intel Corporation 82578DC Gigabit Network
Connection (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 5 (rev 06)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 7 (rev 06)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 8 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface
Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60
[Radeon X300 (PCIE)]
01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
03:00.0 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.1 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.2 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.3 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.4 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.5 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.6 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
03:00.7 USB Controller: NetMos Technology MCS9990 PCIe to 4‐Port USB 2.0
Host Controller
05:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6145 SATA II
PCI-E controller (rev a1)
06:00.0 PCI bridge: Pericom Semiconductor PI7C8140A PCI-to-PCI Bridge
06:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
IEEE-1394a-2000 Controller (PHY/Link)
07:08.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)
07:09.0 Multimedia video controller: Internext Compression Inc iTVC16
(CX23416) MPEG-2 Encoder (rev 01)


$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz
stepping : 5
cpu MHz : 3199.490
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology
nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority
ept vpid
bogomips : 6398.98
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz
stepping : 5
cpu MHz : 3199.490
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology
nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority
ept vpid
bogomips : 6400.15
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz
stepping : 5
cpu MHz : 3199.490
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 2
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology
nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority
ept vpid
bogomips : 6400.17
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz
stepping : 5
cpu MHz : 3199.490
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 2
apicid : 5
initial apicid : 5
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology
nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16
xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority
ept vpid
bogomips : 6400.17
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:


# lshw
media-server
description: Computer
width: 64 bits
capabilities: smbios-2.6 dmi-2.6 vsyscall64 vsyscall32
configuration: boot=normal uuid=63B99640-8D3E-11DF-AF8E-000C6EFF7219
*-core
description: Motherboard
product: DP55KG
vendor: Intel Corporation
physical id: 0
version: AAE47218-405
serial: BTKG0290009Q
slot: Base Board Chassis Location
*-cpu
description: CPU
product: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz
vendor: Intel Corp.
physical id: 0
bus info: cpu@0
version: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz
slot: LGA 1156
size: 3201MHz
capacity: 4GHz
width: 64 bits
clock: 133MHz
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts
rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat
tpr_shadow vnmi flexpriority ept vpid
*-cache:0
description: L3 cache
physical id: 1
slot: Unknown
size: 4MiB
capacity: 4MiB
capabilities: asynchronous internal write-back unified
*-cache:1
description: L2 cache
physical id: 3
slot: Unknown
size: 256KiB
capacity: 256KiB
capabilities: asynchronous internal write-back unified
*-cache:2
description: L1 cache
physical id: 4
slot: Unknown
size: 32KiB
capacity: 32KiB
capabilities: asynchronous internal write-back instruction
*-cache
description: L1 cache
physical id: 2
slot: Unknown
size: 32KiB
capacity: 32KiB
capabilities: asynchronous internal write-back data
*-firmware
description: BIOS
vendor: Intel Corp.
physical id: 5
version: KGIBX10J.86A.4905.2010.0402.1639 (04/02/2010)
size: 64KiB
capacity: 1984KiB
capabilities: pci upgrade shadowing cdboot bootselect edd int9keyboard
int14serial int17printer int10video acpi usb zipboot
biosbootspecification netboot
*-memory
description: System Memory
physical id: 1d
slot: System board or motherboard
size: 4GiB
*-bank:0
description: DIMM Synchronous 1333 MHz (0.8 ns)
product: 0x393930353430332D3135332E4130304C4620
vendor: 0x0198
physical id: 0
serial: 0x5C2DC838
slot: J1MY
size: 2GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:1
description: DIMM Synchronous [empty]
product: NO DIMM
vendor: NO DIMM
physical id: 1
serial: NO DIMM
slot: J2MY
*-bank:2
description: DIMM Synchronous 1333 MHz (0.8 ns)
product: 0x393930353430332D3135332E4130304C4620
vendor: 0x0198
physical id: 2
serial: 0x5D2DCB38
slot: J3MY
size: 2GiB
width: 64 bits
clock: 1333MHz (0.8ns)
*-bank:3
description: DIMM Synchronous [empty]
product: NO DIMM
vendor: NO DIMM
physical id: 3
serial: NO DIMM
slot: J5MY
*-pci
description: Host bridge
product: Core Processor DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 18
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: Core Processor PCI Express x16 Root Port
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 18
width: 32 bits
clock: 33MHz
capabilities: pci pm msi pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:24 ioport:2000(size=4096) memory:f0300000-f03fffff
ioport:e0000000(size=134217728)
*-display:0 UNCLAIMED
description: VGA compatible controller
product: RV370 5B60 [Radeon X300 (PCIE)]
vendor: ATI Technologies Inc
physical id: 0
bus info: pci@0000:01:00.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list
configuration: latency=0
resources: memory:e0000000-e7ffffff(prefetchable) ioport:2000(size=256)
memory:f0310000-f031ffff memory:f0320000-f033ffff(prefetchable)
*-display:1 UNCLAIMED
description: Display controller
product: RV370 [Radeon X300SE]
vendor: ATI Technologies Inc
physical id: 0.1
bus info: pci@0000:01:00.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress bus_master cap_list
configuration: latency=0
resources: memory:f0300000-f030ffff
*-network
description: Ethernet interface
product: 82578DC Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 06
serial: 70:71:bc:63:09:23
size: 1GB/s
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e
driverversion=1.0.2-k2 duplex=full firmware=0.12-5 latency=0 link=yes
multicast=yes port=twisted pair speed=1GB/s
resources: irq:29 memory:f0400000-f041ffff memory:f0420000-f0420fff
ioport:3040(size=32)
*-usb:0
description: USB Controller
product: 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:16 memory:f0421c00-f0421fff
*-pci:1
description: PCI bridge
product: 5 Series/3400 Series Chipset PCI Express Root Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:25 ioport:4000(size=4096) memory:d0000000-d01fffff
memory:d0200000-d03fffff(prefetchable)
*-pci:2
description: PCI bridge
product: 5 Series/3400 Series Chipset PCI Express Root Port 5
vendor: Intel Corporation
physical id: 1c.4
bus info: pci@0000:00:1c.4
version: 06
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:26 ioport:5000(size=4096) memory:f0200000-f02fffff
memory:d0400000-d05fffff(prefetchable)
*-usb:0
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0
bus info: pci@0000:03:00.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ohci bus_master cap_list
configuration: driver=ohci_hcd latency=0
resources: irq:16 memory:f0207000-f0207fff
*-usb:1
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.1
bus info: pci@0000:03:00.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:16 memory:f0206000-f0206fff
*-usb:2
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.2
bus info: pci@0000:03:00.2
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ohci bus_master cap_list
configuration: driver=ohci_hcd latency=0
resources: irq:17 memory:f0205000-f0205fff
*-usb:3
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.3
bus info: pci@0000:03:00.3
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:17 memory:f0204000-f0204fff
*-usb:4
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.4
bus info: pci@0000:03:00.4
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ohci bus_master cap_list
configuration: driver=ohci_hcd latency=0
resources: irq:18 memory:f0203000-f0203fff
*-usb:5
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.5
bus info: pci@0000:03:00.5
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:18 memory:f0202000-f0202fff
*-usb:6
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.6
bus info: pci@0000:03:00.6
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ohci bus_master cap_list
configuration: driver=ohci_hcd latency=0
resources: irq:19 memory:f0201000-f0201fff
*-usb:7
description: USB Controller
product: MCS9990 PCIe to 4‐Port USB 2.0 Host Controller
vendor: NetMos Technology
physical id: 0.7
bus info: pci@0000:03:00.7
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi pm pciexpress ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:19 memory:f0200000-f0200fff
*-pci:3
description: PCI bridge
product: 5 Series/3400 Series Chipset PCI Express Root Port 7
vendor: Intel Corporation
physical id: 1c.6
bus info: pci@0000:00:1c.6
version: 06
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:27 ioport:6000(size=4096) memory:d0600000-d07fffff
memory:d0800000-d09fffff(prefetchable)
*-pci:4
description: PCI bridge
product: 5 Series/3400 Series Chipset PCI Express Root Port 8
vendor: Intel Corporation
physical id: 1c.7
bus info: pci@0000:00:1c.7
version: 06
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:28 ioport:1000(size=4096) memory:f0100000-f01fffff
memory:d0a00000-d0afffff(prefetchable)
*-ide
description: IDE interface
product: 88SE6145 SATA II PCI-E controller
vendor: Marvell Technology Group Ltd.
physical id: 0
bus info: pci@0000:05:00.0
version: a1
width: 32 bits
clock: 33MHz
capabilities: ide pm msi pciexpress bus_master cap_list rom
configuration: driver=pata_marvell latency=0 mingnt=8
resources: irq:19 ioport:1018(size=8) ioport:1024(size=4)
ioport:1010(size=8) ioport:1020(size=4) ioport:1000(size=16)
memory:f0100000-f01003ff memory:d0a00000-d0a3ffff(prefetchable)
*-usb:1
description: USB Controller
product: 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci_hcd latency=0
resources: irq:23 memory:f0421800-f0421bff
*-pci:5
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: a6
width: 32 bits
clock: 33MHz
capabilities: pci subtractive_decode bus_master cap_list
resources: memory:f0000000-f00fffff ioport:e8000000(size=134217728)
*-pci
description: PCI bridge
product: PI7C8140A PCI-to-PCI Bridge
vendor: Pericom Semiconductor
physical id: 0
bus info: pci@0000:06:00.0
version: 00
width: 32 bits
clock: 66MHz
capabilities: pci pm hotswap normal_decode bus_master cap_list
resources: ioport:e8000000(size=134217728)
*-multimedia:0
description: Multimedia video controller
product: iTVC16 (CX23416) MPEG-2 Encoder
vendor: Internext Compression Inc
physical id: 8
bus info: pci@0000:07:08.0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=ivtv latency=64 maxlatency=8 mingnt=128
resources: irq:21 memory:ec000000-efffffff(prefetchable)
*-multimedia:1
description: Multimedia video controller
product: iTVC16 (CX23416) MPEG-2 Encoder
vendor: Internext Compression Inc
physical id: 9
bus info: pci@0000:07:09.0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=ivtv latency=64 maxlatency=8 mingnt=128
resources: irq:22 memory:e8000000-ebffffff(prefetchable)
*-firewire
description: FireWire (IEEE 1394)
product: TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
vendor: Texas Instruments
physical id: 3
bus info: pci@0000:06:03.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm ohci bus_master cap_list
configuration: driver=firewire_ohci latency=32 maxlatency=4 mingnt=2
resources: irq:19 memory:f0004000-f00047ff memory:f0000000-f0003fff
*-isa
description: ISA bridge
product: 5 Series Chipset LPC Interface Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: latency=0
*-storage
description: SATA controller
product: 5 Series/3400 Series Chipset 6 port SATA AHCI Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
logical name: scsi0
logical name: scsi1
logical name: scsi2
logical name: scsi3
logical name: scsi4
logical name: scsi5
version: 06
width: 32 bits
clock: 66MHz
capabilities: storage msi pm ahci_1.0 bus_master cap_list emulated
configuration: driver=ahci latency=0
resources: irq:30 ioport:3068(size=8) ioport:3074(size=4)
ioport:3060(size=8) ioport:3070(size=4) ioport:3020(size=32)
memory:f0421000-f04217ff
*-disk:0
description: ATA Disk
product: WDC WD5000BUDT-6
vendor: Western Digital
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: 01.0
serial: WD-WXG1A70T6993
size: 465GiB (500GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=000a0314
*-volume:0
description: EXT4 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
logical name: /boot
version: 1.0
serial: b220f2b9-85c6-41bc-b509-af1413dfe5c5
size: 1028MiB
capacity: 1028MiB
capabilities: primary bootable journaled extended_attributes large_files
huge_files dir_nlink extents ext4 ext2 initialized
configuration: created=2011-04-26 18:15:37 filesystem=ext4
label=sys-boot lastmountpoint=/boot�*����,_N$�(���PU@ ���$
modified=2011-05-15 14:28:56 mount.fstype=ext4
mount.options=rw,noatime,barrier=1,data=ordered mounted=2011-04-30
19:42:24 state=mounted
*-volume:1
description: Linux swap volume
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
version: 1
serial: 83388e3d-8102-4138-ab30-171291d303c5
size: 4103MiB
capacity: 4103MiB
capabilities: primary nofs swap initialized
configuration: filesystem=swap pagesize=4096
*-volume:2
description: EXT4 volume
vendor: Linux
physical id: 3
bus info: scsi@0:0.0.0,3
logical name: /dev/sda3
logical name: /
version: 1.0
serial: 70f8353b-b3bd-4590-83a0-5820778f235d
size: 5126MiB
capacity: 5126MiB
capabilities: primary journaled extended_attributes large_files
huge_files dir_nlink recover extents ext4 ext2 initialized
configuration: created=2011-04-26 18:15:38 filesystem=ext4
label=sys-root lastmountpoint=/q�(�����!!@[(������)���!
modified=2011-04-30 18:07:50 mount.fstype=ext4
mount.options=rw,noatime,errors=remount-ro,barrier=1,data=ordered
mounted=2011-05-15 14:29:46 state=mounted
*-volume:3
description: Extended partition
physical id: 4
bus info: scsi@0:0.0.0,4
logical name: /dev/sda4
size: 455GiB
capacity: 455GiB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume:0
description: Linux filesystem partition
physical id: 5
logical name: /dev/sda5
logical name: /usr
capacity: 10GiB
configuration: mount.fstype=ext4
mount.options=rw,noatime,barrier=1,data=ordered state=mounted
*-logicalvolume:1
description: Linux filesystem partition
physical id: 6
logical name: /dev/sda6
logical name: /var
capacity: 10GiB
configuration: mount.fstype=ext4
mount.options=rw,noatime,barrier=1,data=ordered state=mounted
*-logicalvolume:2
description: Linux filesystem partition
physical id: 7
logical name: /dev/sda7
logical name: /home
capacity: 10GiB
configuration: mount.fstype=ext4
mount.options=rw,noatime,barrier=1,data=ordered state=mounted
*-logicalvolume:3
description: Linux filesystem partition
physical id: 8
logical name: /dev/sda8
logical name: /tmp
capacity: 1028MiB
configuration: mount.fstype=ext4
mount.options=rw,noatime,barrier=1,data=ordered state=mounted
*-logicalvolume:4
description: Linux LVM Physical Volume partition
physical id: 9
logical name: /dev/sda9
serial: uqsVSD-NKAi-HIt1-7H2N-RP7q-upTy-1WmGvQ
size: 424GiB
capacity: 424GiB
capabilities: multi lvm2
*-disk:1
description: ATA Disk
product: WDC WD20EARS-00M
vendor: Western Digital
physical id: 1
bus info: scsi@1:0.0.0
logical name: /dev/sdb
version: 51.0
serial: WD-WCAZA1793361
size: 1863GiB (2TB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=00068338
*-volume
description: Linux filesystem partition
physical id: 1
bus info: scsi@1:0.0.0,1
logical name: /dev/sdb1
logical name: /mnt/recordings
logical name: /home/hoferr/Media/Aufzeichnungen
capacity: 1863GiB
capabilities: primary bootable
configuration: mount.fstype=jfs mount.options=rw,noatime state=mounted
*-disk:2
description: ATA Disk
product: SAMSUNG HD154UI
physical id: 2
bus info: scsi@2:0.0.0
logical name: /dev/sdc
version: 1AG0
serial: S1XWJ1KSC07338
size: 1397GiB (1500GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=0007694c
*-volume
description: Linux raid autodetect partition
physical id: 1
bus info: scsi@2:0.0.0,1
logical name: /dev/sdc1
capacity: 1397GiB
capabilities: primary multi
*-disk:3
description: ATA Disk
product: SAMSUNG HD154UI
physical id: 3
bus info: scsi@3:0.0.0
logical name: /dev/sdd
version: 1AG0
serial: S1XWJ9AS800055
size: 1397GiB (1500GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=00097014
*-volume
description: Linux raid autodetect partition
physical id: 1
bus info: scsi@3:0.0.0,1
logical name: /dev/sdd1
capacity: 1397GiB
capabilities: primary multi
*-disk:4
description: ATA Disk
product: SAMSUNG HD154UI
physical id: 4
bus info: scsi@4:0.0.0
logical name: /dev/sde
version: 1AG0
serial: S1XWJ1KSC07339
size: 1397GiB (1500GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=000beebc
*-volume
description: Linux raid autodetect partition
physical id: 1
bus info: scsi@4:0.0.0,1
logical name: /dev/sde1
capacity: 1397GiB
capabilities: primary multi
*-disk:5
description: ATA Disk
product: SAMSUNG HD154UI
physical id: 5
bus info: scsi@5:0.0.0
logical name: /dev/sdf
version: 1AG0
serial: S1XWJ1KSC07340
size: 1397GiB (1500GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=000da169
*-volume
description: Linux raid autodetect partition
physical id: 1
bus info: scsi@5:0.0.0,1
logical name: /dev/sdf1
capacity: 1397GiB
capabilities: primary multi
*-serial
description: SMBus
product: 5 Series/3400 Series Chipset SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 06
width: 64 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0
resources: irq:18 memory:f0422000-f04220ff ioport:3000(size=32)


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: WinTV PVR-500 stops recording after some minutes (ivtv0: DMA TIMEOUT) [ In reply to ]
awalls at md
May 15, 2011, 1:31 PM
Post #2 of 6 (3895 views)
Permalink
On Sun, 2011-05-15 at 14:48 +0200, Ramon Hofer wrote:
> Hi list
>
> I have a WinTV PVR 500 and the "ivtv0: DMA TIMEOUT" problem which I'm
> trying to solve for several months now.
> After reading through wikis, forum and mailing posts but I'm still not
> sure where the problem could be.

Here's the fix:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d213ad08362909ab50fbd6568fcc9fd568268d29

I'm not sure what kernel version it went into, but it is certainly not
in kernel v2.6.32.


> Maybe I'll have to send the card back
> as it could be broken or maybe there's just a little configuration I
> can't get right?

Nope. It's an ivtv driver bug in the way a DMA_TIMEOUT error condition
is handled.

The exact reason why you get DMA_TIMEOUT errors in the first place is a
function of your system hardware and its configuration and use. Usually
one of the PCI bridges is to blame. There is nothing that can usefully
be done in the ivtv driver about that, since it is a system level issue.


> I'd really appreciate any help :-)


> $ uname -a
> Linux media-server 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011
> x86_64 GNU/Linux

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: WinTV PVR-500 stops recording after some minutes (ivtv0: DMA TIMEOUT) [ In reply to ]
ramonhofer at bluewin
May 16, 2011, 7:45 AM
Post #3 of 6 (3886 views)
Permalink
Hi Andy

Thank you so much for your reply!

On 05/15/2011 10:31 PM, Andy Walls wrote:
> On Sun, 2011-05-15 at 14:48 +0200, Ramon Hofer wrote:
>> Hi list
>>
>> I have a WinTV PVR 500 and the "ivtv0: DMA TIMEOUT" problem which I'm
>> trying to solve for several months now.
>> After reading through wikis, forum and mailing posts but I'm still not
>> sure where the problem could be.
> Here's the fix:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d213ad08362909ab50fbd6568fcc9fd568268d29
>
> I'm not sure what kernel version it went into, but it is certainly not
> in kernel v2.6.32.

Is it correct that this is a kernel patch?
If so I'd have to download the kernel source, apply the patch and
compile it?

I have never done this before and I don't know if it wouldn't be easier
to just use a newer kernel?
I'll ask in the debian mailing list...


>> Maybe I'll have to send the card back
>> as it could be broken or maybe there's just a little configuration I
>> can't get right?
> Nope. It's an ivtv driver bug in the way a DMA_TIMEOUT error condition
> is handled.
>
> The exact reason why you get DMA_TIMEOUT errors in the first place is a
> function of your system hardware and its configuration and use. Usually
> one of the PCI bridges is to blame. There is nothing that can usefully
> be done in the ivtv driver about that, since it is a system level issue.

I'm just curious: When there's nothing that can be done, what does the
patch do?

If I understand it right the PCI bridge on my mainboard doesn't work as
it should.
So the driver just retries three times and ignores any failure?



Thanks again
Ramon

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: WinTV PVR-500 stops recording after some minutes (ivtv0: DMA TIMEOUT) [ In reply to ]
ramonhofer at bluewin
May 16, 2011, 12:09 PM
Post #4 of 6 (3891 views)
Permalink
Thank you again Andy


On 05/15/2011 10:31 PM, Andy Walls wrote:
> On Sun, 2011-05-15 at 14:48 +0200, Ramon Hofer wrote:
>> Hi list
>>
>> I have a WinTV PVR 500 and the "ivtv0: DMA TIMEOUT" problem which I'm
>> trying to solve for several months now.
>> After reading through wikis, forum and mailing posts but I'm still not
>> sure where the problem could be.
> Here's the fix:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d213ad08362909ab50fbd6568fcc9fd568268d29
>
> I'm not sure what kernel version it went into, but it is certainly not
> in kernel v2.6.32.

I don't want to do anything wrong so I'd like to ask if this is correct
to patch kernel version 2.6.32-5-amd64:
I found this Debian kernel handbook:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html

# apt-get install linux-source-2.6.32
$ cd ~/System
$ tar jxf /usr/src/linux-source-2.6.32.tar.bz2

But when I try to apply the patch I get the following:
$ patch -p1 < ivtv.patch
patching file drivers/media/video/ivtv/ivtv-irq.c
Hunk #1 FAILED at 628.
1 out of 1 hunk FAILED -- saving rejects to file
drivers/media/video/ivtv/ivtv-irq.c.rej


I created ivtv.patch which contains:

$ cat ivtv.patch
diff --git a/drivers/media/video/ivtv/ivtv-irq.c
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9b4faf009196afad6de8f4b3ffeebc0dbd2f05e6>
b/drivers/media/video/ivtv/ivtv-irq.c
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9c29e964d400b955d36074487c17c22e1195bbcd;hb=d213ad08362909ab50fbd6568fcc9fd568268d29>
index 9b4faf0
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9b4faf009196afad6de8f4b3ffeebc0dbd2f05e6>..9c29e96
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9c29e964d400b955d36074487c17c22e1195bbcd;hb=d213ad08362909ab50fbd6568fcc9fd568268d29>
100644(file)
--- a/drivers/media/video/ivtv/ivtv-irq.c
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9b4faf009196afad6de8f4b3ffeebc0dbd2f05e6>
+++ b/drivers/media/video/ivtv/ivtv-irq.c
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9c29e964d400b955d36074487c17c22e1195bbcd;hb=d213ad08362909ab50fbd6568fcc9fd568268d29>
@@ -628,22
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9b4faf009196afad6de8f4b3ffeebc0dbd2f05e6#l628>
+628,66
<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/media/video/ivtv/ivtv-irq.c;h=9c29e964d400b955d36074487c17c22e1195bbcd;hb=d213ad08362909ab50fbd6568fcc9fd568268d29#l628>
@@ static void ivtv_irq_enc_pio_complete(struct ivtv *itv)
static void ivtv_irq_dma_err(struct ivtv *itv)
{
u32 data[CX2341X_MBOX_MAX_DATA];
+ u32 status;
del_timer(&itv->dma_timer);
+
ivtv_api_get_data(&itv->enc_mbox, IVTV_MBOX_DMA_END, 2, data);
+ status = read_reg(IVTV_REG_DMASTATUS);
IVTV_DEBUG_WARN("DMA ERROR %08x %08x %08x %d\n", data[0], data[1],
- read_reg(IVTV_REG_DMASTATUS), itv->cur_dma_stream);
- write_reg(read_reg(IVTV_REG_DMASTATUS) & 3, IVTV_REG_DMASTATUS);
+ status, itv->cur_dma_stream);
+ /*
+ * We do *not* write back to the IVTV_REG_DMASTATUS register to
+ * clear the error status, if either the encoder write (0x02) or
+ * decoder read (0x01) bus master DMA operation do not indicate
+ * completed. We can race with the DMA engine, which may have
+ * transitioned to completed status *after* we read the register.
+ * Setting a IVTV_REG_DMASTATUS flag back to "busy" status, after the
+ * DMA engine has completed, will cause the DMA engine to stop working.
+ */
+ status &= 0x3;
+ if (status == 0x3)
+ write_reg(status, IVTV_REG_DMASTATUS);
+
if (!test_bit(IVTV_F_I_UDMA, &itv->i_flags) &&
itv->cur_dma_stream >= 0 && itv->cur_dma_stream
< IVTV_MAX_STREAMS) {
struct ivtv_stream *s = &itv->streams[itv->cur_dma_stream];
- /* retry */
- if (s->type >= IVTV_DEC_STREAM_TYPE_MPG)
+ if (s->type >= IVTV_DEC_STREAM_TYPE_MPG) {
+ /* retry */
+ /*
+ * FIXME - handle cases of DMA error similar to
+ * encoder below, except conditioned on status & 0x1
+ */
ivtv_dma_dec_start(s);
- else
- ivtv_dma_enc_start(s);
- return;
+ return;
+ } else {
+ if ((status & 0x2) == 0) {
+ /*
+ * CX2341x Bus Master DMA write is ongoing.
+ * Reset the timer and let it complete.
+ */
+ itv->dma_timer.expires =
+ jiffies + msecs_to_jiffies(600);
+ add_timer(&itv->dma_timer);
+ return;
+ }
+
+ if (itv->dma_retries < 3) {
+ /*
+ * CX2341x Bus Master DMA write has ended.
+ * Retry the write, starting with the first
+ * xfer segment. Just retrying the current
+ * segment is not sufficient.
+ */
+ s->sg_processed = 0;
+ itv->dma_retries++;
+ ivtv_dma_enc_start_xfer(s);
+ return;
+ }
+ /* Too many retries, give up on this one */
+ }
+
}
if (test_bit(IVTV_F_I_UDMA, &itv->i_flags)) {
ivtv_udma_start(itv);


The rejects which were save to the file
drivers/media/video/ivtv/ivtv-irq.c.rej are:

$ cat drivers/media/video/ivtv/ivtv-irq.c.rej
--- drivers/media/video/ivtv/ivtv-irq.c
+++ drivers/media/video/ivtv/ivtv-irq.c
@@ -628,22 +628,66 @@
static void ivtv_irq_dma_err(struct ivtv *itv)
{
u32 data[CX2341X_MBOX_MAX_DATA];
+ u32 status;

del_timer(&itv->dma_timer);
+
ivtv_api_get_data(&itv->enc_mbox, IVTV_MBOX_DMA_END, 2, data);
+ status = read_reg(IVTV_REG_DMASTATUS);
IVTV_DEBUG_WARN("DMA ERROR %08x %08x %08x %d\n", data[0], data[1],
- read_reg(IVTV_REG_DMASTATUS),
itv->cur_dma_stream);
- write_reg(read_reg(IVTV_REG_DMASTATUS) & 3, IVTV_REG_DMASTATUS);
+ status, itv->cur_dma_stream);
+ /*
+ * We do *not* write back to the IVTV_REG_DMASTATUS register to
+ * clear the error status, if either the encoder write (0x02) or
+ * decoder read (0x01) bus master DMA operation do not indicate
+ * completed. We can race with the DMA engine, which may have
+ * transitioned to completed status *after* we read the register.
+ * Setting a IVTV_REG_DMASTATUS flag back to "busy" status,
after the
+ * DMA engine has completed, will cause the DMA engine to stop
working.
+ */
+ status &= 0x3;
+ if (status == 0x3)
+ write_reg(status, IVTV_REG_DMASTATUS);
+
if (!test_bit(IVTV_F_I_UDMA, &itv->i_flags) &&
itv->cur_dma_stream >= 0 && itv->cur_dma_stream <
IVTV_MAX_STREAMS) {
struct ivtv_stream *s = &itv->streams[itv->cur_dma_stream];

- /* retry */
- if (s->type >= IVTV_DEC_STREAM_TYPE_MPG)
+ if (s->type >= IVTV_DEC_STREAM_TYPE_MPG) {
+ /* retry */
+ /*
+ * FIXME - handle cases of DMA error similar to
+ * encoder below, except conditioned on status & 0x1
+ */
ivtv_dma_dec_start(s);
- else
- ivtv_dma_enc_start(s);
- return;
+ return;
+ } else {
+ if ((status & 0x2) == 0) {
+ /*
+ * CX2341x Bus Master DMA write is ongoing.
+ * Reset the timer and let it complete.
+ */
+ itv->dma_timer.expires =
+ jiffies +
msecs_to_jiffies(600);
+ add_timer(&itv->dma_timer);
+ return;
+ }
+
+ if (itv->dma_retries < 3) {
+ /*
+ * CX2341x Bus Master DMA write has ended.
+ * Retry the write, starting with the first
+ * xfer segment. Just retrying the current
+ * segment is not sufficient.
+ */
+ s->sg_processed = 0;
+ itv->dma_retries++;
+ ivtv_dma_enc_start_xfer(s);
+ return;
+ }
+ /* Too many retries, give up on this one */
+ }
+
}
if (test_bit(IVTV_F_I_UDMA, &itv->i_flags)) {
ivtv_udma_start(itv);


When I look for the differences between the two files I get:

$ diff ivtv.patch drivers/media/video/ivtv/ivtv-irq.c.rej
1,5c1,3
< diff --git a/drivers/media/video/ivtv/ivtv-irq.c
b/drivers/media/video/ivtv/ivtv-irq.c
< index 9b4faf0..9c29e96 100644 (file)
< --- a/drivers/media/video/ivtv/ivtv-irq.c
< +++ b/drivers/media/video/ivtv/ivtv-irq.c
< @@ -628,22 +628,66 @@ static void ivtv_irq_enc_pio_complete(struct
ivtv *itv)
---
> --- drivers/media/video/ivtv/ivtv-irq.c
> +++ drivers/media/video/ivtv/ivtv-irq.c
> @@ -628,22 +628,66 @@
79d76
<


Best regards
Ramon
Re: WinTV PVR-500 stops recording after some minutes (ivtv0: DMA TIMEOUT) [ In reply to ]
awalls at md
May 16, 2011, 4:20 PM
Post #5 of 6 (3871 views)
Permalink
On Mon, 2011-05-16 at 21:09 +0200, Ramon Hofer wrote:
> Thank you again Andy
>
>
> On 05/15/2011 10:31 PM, Andy Walls wrote:
> > On Sun, 2011-05-15 at 14:48 +0200, Ramon Hofer wrote:
> > > Hi list
> > >
> > > I have a WinTV PVR 500 and the "ivtv0: DMA TIMEOUT" problem which I'm
> > > trying to solve for several months now.
> > > After reading through wikis, forum and mailing posts but I'm still not
> > > sure where the problem could be.
> > Here's the fix:
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d213ad08362909ab50fbd6568fcc9fd568268d29
> >
> > I'm not sure what kernel version it went into, but it is certainly not
> > in kernel v2.6.32.
>
> I don't want to do anything wrong so I'd like to ask if this is
> correct to patch kernel version 2.6.32-5-amd64:
> I found this Debian kernel handbook:
> http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
>
> # apt-get install linux-source-2.6.32
> $ cd ~/System
> $ tar jxf /usr/src/linux-source-2.6.32.tar.bz2
>
> But when I try to apply the patch I get the following:
> $ patch -p1 < ivtv.patch
> patching file drivers/media/video/ivtv/ivtv-irq.c
> Hunk #1 FAILED at 628.
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/media/video/ivtv/ivtv-irq.c.rej

Hi Ramon,

The entire patch failed to be applied. The patch was made against a
kernel more recent than the 2.6.32 version you are using, and the file
ivtv-irq.c is too different.

You have a few choices:

1. Adapt the patch by hand applying the needed changes to the ivtv-irq.c
source code file in your old kernel version (2.6.32). Then compile the
kernel and modules and install the ivtv driver module.

or

2. Upgrade to at least kernel version 2.6.37.4. This seems to be the
earliest "stable" kernel to which the patch has been backported and
officially released.

http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.37.4

You shouldn't need to patch the kernel or build the kernel, if debian
provides a 2.6.37.4 kernel image package for you.

or

3. Build the bleeding edge v4l-dvb drivers against your kernl and
install them. There are no guarantees on this working well for any
particular kernel version:

http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers


I will not recommend #3 for you, unless you are *very* comfortable with
building modules from source and dealing with build failures.


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
Re: WinTV PVR-500 stops recording after some minutes (ivtv0: DMA TIMEOUT) [ In reply to ]
awalls at md
May 17, 2011, 2:09 PM
Post #6 of 6 (3893 views)
Permalink
Ramon Hofer <ramonhofer@bluewin.ch> wrote:

>On 05/17/2011 02:02 AM, Andy Walls wrote:
>> On Mon, 2011-05-16 at 21:09 +0200, Ramon Hofer wrote:
>>> Thank you again Andy
>>>
>>>
>>> On 05/15/2011 10:31 PM, Andy Walls wrote:
>>>> On Sun, 2011-05-15 at 14:48 +0200, Ramon Hofer wrote:
>>>>> Hi list
>>>>>
>>>>> I have a WinTV PVR 500 and the "ivtv0: DMA TIMEOUT" problem which
>I'm
>>>>> trying to solve for several months now.
>>>>> After reading through wikis, forum and mailing posts but I'm still
>not
>>>>> sure where the problem could be.
>>>> Here's the fix:
>>>>
>>>>
>http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d213ad08362909ab50fbd6568fcc9fd568268d29
>>>>
>>>> I'm not sure what kernel version it went into, but it is certainly
>not
>>>> in kernel v2.6.32.
>>> I don't want to do anything wrong so I'd like to ask if this is
>>> correct to patch kernel version 2.6.32-5-amd64:
>>> I found this Debian kernel handbook:
>>> http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
>>>
>>> # apt-get install linux-source-2.6.32
>>> $ cd ~/System
>>> $ tar jxf /usr/src/linux-source-2.6.32.tar.bz2
>>>
>>> But when I try to apply the patch I get the following:
>>> $ patch -p1< ivtv.patch
>>> patching file drivers/media/video/ivtv/ivtv-irq.c
>>> Hunk #1 FAILED at 628.
>>> 1 out of 1 hunk FAILED -- saving rejects to file
>>> drivers/media/video/ivtv/ivtv-irq.c.rej
>> Hi Ramon,
>>
>> The entire patch failed to be applied. The patch was made against a
>> kernel more recent than the 2.6.32 version you are using, and the
>file
>> ivtv-irq.c is too different.
>>
>> You have a few choices:
>>
>> 1. Adapt the patch by hand applying the needed changes to the
>ivtv-irq.c
>> source code file in your old kernel version (2.6.32). Then compile
>the
>> kernel and modules and install the ivtv driver module.
>>
>> or
>>
>> 2. Upgrade to at least kernel version 2.6.37.4. This seems to be the
>> earliest "stable" kernel to which the patch has been backported and
>> officially released.
>>
>> http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.37.4
>>
>> You shouldn't need to patch the kernel or build the kernel, if debian
>> provides a 2.6.37.4 kernel image package for you.
>>
>> or
>>
>> 3. Build the bleeding edge v4l-dvb drivers against your kernl and
>> install them. There are no guarantees on this working well for any
>> particular kernel version:
>>
>>
>http://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
>>
>>
>> I will not recommend #3 for you, unless you are *very* comfortable
>with
>> building modules from source and dealing with build failures.
>>
>>
>> Regards,
>> Andy
>>
>>
>
>I went for the second choice and installed kernel 2.6.38 from the
>debian
>backports.
>The PVR-500 seems to work fine now.
>I'm going to test it intensively :-)
>
>Unfortunately I have problems with my other card (TeVii S480 and
>s2-liplianin).
>But this belongs somewhere else I suppose.
>
>
>Thanks again
>Ramon

Yes: linux-media@vger.kernel.org

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal