[Xen-bugs] [Bug 804] New: ivtv swiotlb DMA problems

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=804

           Summary: ivtv swiotlb DMA problems
           Product: Xen
           Version: 3.0.2
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Hardware Support
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ericgalis@xxxxxxxxx


I am currently running xen-3.0.2 with kernel with a 2.6.16.28-xen kernel custom
compiled in gentoo.  I am trying to use a Hauppauge capture card (pvr-500) in a
domU. First, I would get this error when running depmod ivtv:

------------[ cut here ]------------
kernel BUG at arch/i386/kernel/pci-dma-xen.c:298!
invalid opcode: 0000 [#1]
Modules linked in: wm8775 cx25840 tda9887 tuner ivtv firmware_class
i2c_algo_bit tveeprom i2c_core
CPU:    0
EIP:    0061:[<c010853e>]    Not tainted VLI
EFLAGS: 00010296   (2.6.16.28-xen #4)
EIP is at dma_map_single+0xc7/0x105
eax: 0000002f   ebx: 00000000   ecx: 00000000   edx: ffffff82
esi: 29eeb000   edi: 00008100   ebp: c00be848   esp: df5e3cdc
ds: 007b   es: 007b   ss: 0069
Process modprobe (pid: 3989, threadinfo=df5e2000 task=c16cd070)
Stack: <0>c0396ce8 df6e91e0 df6e91e0 00000002 dec50000 e10d05b2 c00be848
dec90000
       00008100 00000002 df7b7000 00000600 00400000 00000000 e10d1922 dec50000
       df7b7000 00000080 00000000 00000000 df7b7000 df7b705c dec50000 dec50000
Call Trace:
 [<e10d05b2>] ivtv_init_buffer+0x163/0x174 [ivtv]
 [<e10d1922>] ivtv_stream_alloc+0x27d/0x3b2 [ivtv]
 [<e10cda23>] ivtv_streams_setup+0x326/0x35e [ivtv]
 [<e10c8d21>] ivtv_probe+0x1420/0x17ab [ivtv]
 [<c011d9a2>] call_usermodehelper_keys+0xae/0xba
 [<c011d9ae>] __call_usermodehelper+0x0/0x44
 [<c0262213>] pci_match_device+0x15/0x94
 [<c02623f5>] pci_device_probe+0x38/0x5b
 [<c0289106>] driver_probe_device+0x42/0x92
 [<c02891ad>] __driver_attach+0x0/0x5c
 [<c02891e4>] __driver_attach+0x37/0x5c
 [<c0288c16>] bus_for_each_dev+0x47/0x6d
 [<c028906b>] driver_attach+0x14/0x18
 [<c02891ad>] __driver_attach+0x0/0x5c
 [<c02888d4>] bus_add_driver+0x6e/0x106
 [<c02893ee>] driver_register+0x59/0x76
 [<c0262541>] __pci_register_driver+0x5e/0x82
 [<e10c7683>] module_start+0xbc/0xe2 [ivtv]
 [<c01263a5>] sys_init_module+0x12a7/0x1417
 [<e1096000>] tda9887_fixup_std+0x0/0x4ab [tda9887]
 [<c01207c3>] autoremove_wake_function+0x0/0x3a
 [<c044c7ac>] populate_rootfs+0x5e3/0x91f
 [<c01434da>] vfs_read+0xdb/0x11b
 [<c0143486>] vfs_read+0x87/0x11b
 [<c01437f3>] sys_read+0x3b/0x64
 [<c0104495>] syscall_call+0x7/0xb
Code: ff 0f 00 00 8d 04 3b c1 e6 0c 09 d6 3d 00 10 00 00 76 21 a1 60 66 46 c0
0f a3 08 19 c0 85 c0 75 13 68 e8 6c 39 c0 e8 1f 9c 00 00 <0f> 0b 2a 01 c9 6c 39
c0 5a 85 ed 74 0e 8b 85 f0 00 00 00 85 c0
 Segmentation fault

When I try to force swiotlb with extra="swiotlb=16,force" in the config file
for the domU, I get a kernel panic:

kernel BUG at lib/../arch/i386/kernel/swiotlb.c:152!
invalid opcode: 0000 [#1]
Modules linked in:
CPU:    0
EIP:    e019:[<c025e8bf>]    Not tainted VLI
EFLAGS: 00010282   (2.6.16.28-xen #4)
EIP is at swiotlb_init_with_default_size+0x80/0x167
eax: fffffff4   ebx: 00000000   ecx: 00000001   edx: 00000000
esi: 01000000   edi: c0087108   ebp: 00000000   esp: c0449fc0
ds: e021   es: e021   ss: e021
Process swapper (pid: 0, threadinfo=c0448000 task=c03eac60)
Stack: <0>00000000 c050d000 c0087108 c025ea09 04000000 00000000 c044fa5b
0000000e
       00000002 00000000 c050d000 00000000 00000000 c044a46f c0466380 c010006f
Call Trace:
 [<c025ea09>] swiotlb_init+0x63/0x72
 [<c044fa5b>] mem_init+0x5c/0x2ad
 [<c044a46f>] start_kernel+0xdc/0x226
Code: c0 75 0a 68 17 32 3b c0 e8 53 2f eb ff 8d 56 ff 83 c9 ff c1 ea 0b 41 d1
ea 75 fb 6a 1f 51 50 e8 0d f4 ea ff 83 c4 0c 85 c0 74 08 <0f> 0b 98 00 6c 31 3b
c0 68 00 00 00 01 a1 34 37 47 c0 6a 40 c1
 <0>Kernel panic - not syncing: Attempted to kill the idle task!

extra="swiotlb=force", extra="swiotlb=32,force", and extra="swiotlb=64,force"
all result in the same kernel panic.  I have searched and searched and found no
resolutions for this issue.

Thoughts?


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs