[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] [Fwd: Problems with ivtv module in domU]

Hi, I'm trying to get my system up with a Mythtv backend in a domU,

inspired by this <http://wiki.xensource.com/xenwiki/CoolConfigurations> page. I'm hitting some problems when loading the ivtv driver, and can't seem to get rid of the problem.

I read a interesting post <http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00229.html> on the mailing-list, but it's quite old now, and probably does not apply for the recent drivers / kernels
Here's the relevant parts of configuration/logs:

dom0 lspci:
03:0c.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 
Encoder (rev 01)

dom0 boot param:
vmlinuz-2.6.18-3-xen-686 root=/dev/md2 ro console=tty0 pciback.hide=(03:0c.0)

domU lspci:
00:00.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 
Encoder (rev 01)

domU boot config:
pci = [ '03:0c.0' ]

modprobe ivtv on domU gives:
------------[ cut here ]------------
kernel BUG at arch/i386/kernel/:pci-dma-xen.c309!
invalid opcode: 0000 [#1]
Modules linked in: msp3400 saa7127 saa7115 tda9887 tuner v4l2_common ivtv firmware_class i2c_algo_bit v4l1_compat tveeprom i2c_core videodev
CPU:    0
EIP:    0061:[<c010a5e0>]    Not tainted VLI
EFLAGS: 00010296   ( #4)
EIP is at dma_map_single+0x10e/0x162
eax: 0000002f   ebx: 1ef35000   ecx: c02cca30   edx: 00000000
esi: 00000000   edi: 00008100   ebp: c1655048   esp: df5d1d88
ds: 007b   es: 007b   ss: 0069
Process modprobe (pid: 2677, threadinfo=df5d0000 task=c1643570)
Stack: <0>c02a42b8 c041c7c0 000000d0 00000000 1ef35000 c1655048 c1655000 c16843c0 00000002 e1078086 00000002 c164369c 00000000 00000000 00000080 df394060 e1078189 e036c720 00000000 df320000 00008000 00000000 df320000 df394000
Call Trace:
[<e1078086>] ivtv_init_buffer+0xcd/0x1a4 [ivtv]
[<e1078189>] ivtv_init_queue_nolock+0x2c/0x8e [ivtv]
[<e107822e>] ivtv_init_queues_nolock+0x43/0x6f [ivtv]
[<e10795b8>] ivtv_stream_alloc+0xe5/0x29c [ivtv]
[<e1072dbf>] ivtv_streams_setup+0xec/0x191 [ivtv]
[<e106dac8>] ivtv_probe+0x3a1/0xac7 [ivtv]
[<c012ad75>] __call_usermodehelper+0x0/0x60
[<c01e3249>] pci_call_probe+0xa/0xc
[<c01e329a>] __pci_device_probe+0x4f/0x5d
[<c01e32ce>] pci_device_probe+0x26/0x4d
[<c02003ce>] driver_probe_device+0x64/0xb8
[<c0200507>] __driver_attach+0x84/0x86
[<c01ffa7f>] bus_for_each_dev+0x39/0x57
[<c020051f>] driver_attach+0x16/0x1a
[<c0200483>] __driver_attach+0x0/0x86
[<c01fff06>] bus_add_driver+0x7b/0xbc
[<c01e34b6>] __pci_register_driver+0x58/0x81
[<c011b1cd>] printk+0x17/0x1b
[<e106e743>] module_start+0x97/0x10d [ivtv]
[<c013669a>] sys_init_module+0x12d/0x1d4
[<c0104c45>] syscall_call+0x7/0xb
Code: 24 18 8b 44 24 10 8b 7c 24 1c 8b 6c 24 20 83 c4 24 c3 0f 0b 2e 01 98 42 2a c0 e9 24 ff ff ff c7 04 24 b8 42 2a c0 e8 d6 0b 01 00 <0f> 0b 35 01 98 42 2a c0 e9 6a ff ff ff c7 44 24 0c 2f 01 00 00
Segmentation fault

domU dmesg:
Linux video capture interface: v1.00
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.6.6 (tagged release) loading
ivtv:  Linux version: SMP PENTIUM4 REGPARM gcc-3.4
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 WinTV PVR-350 card (cx23415 based)
PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
tveeprom 0-0050: The eeprom says no radio is present, but the tuner type
tveeprom 0-0050: indicates otherwise. I will assume that radio is present.
tveeprom 0-0050: Hauppauge model 48139, rev K257, serial# 8205817
tveeprom 0-0050: tuner model is Philips FM1216 ME MK3 (idx 57, type 38)
tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
tveeprom 0-0050: audio processor is MSP4418 (idx 25)
tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
tveeprom 0-0050: has radio, has IR remote
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tda9887 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0)
msp3400 0-0040: MSP4418G-B3 supports nicam and radio, mode is autodetect and autoselect
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Decoder revision: 0x02020023
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Fatal DMA error! Please use 'swiotlb=force'

mythbackend ~ # modinfo ivtv
filename:       /lib/modules/
author:         Kevin Thayer, Chris Kennedy, Hans Verkuil
description:    CX23415/CX23416 driver
license:        GPL
version:        0.6.6 (tagged release)
vermagic: SMP PENTIUM4 REGPARM gcc-3.4

I think that should cover it. The dom0 runs Debian Etch, domU runs Gentoo 2006.1

I've also tried to use a Debian Etch domU using the same kernel as the dom0, and the appropriate ivtv driver for the 2.6.18 kernel, and the result is the same.. seems like a problem with pci-dma-xen.c

The swiotlb=force option gives a kernel panic upon booting the domU.

Besides this error, the machine is working great with a separate domain acting as a firewall/router, and another one controlling my raid-pci devices, using pciback.hide..

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.