WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] xen 2.0 testing / DMA failure with ivtv-driver

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen 2.0 testing / DMA failure with ivtv-driver
From: "Manuel Bernhardt" <mailinglist@xxxxxxxxxxx>
Date: Wed, 5 Oct 2005 16:43:03 +0200 (CEST)
Delivery-date: Wed, 05 Oct 2005 14:41:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: OverLook/1.4.3a
Hi everyone,

i'm currently try migrate my mythtv-server into an xen maschine but the
ivtv-driver for my Hauppauge PVR350  doesn't work. Now, a lot of googling
and reading later i'm now here.
I've an error which i can't exactly allocate: is it an driver or an xen
generated error ?

I got with the ivtv-drivers following error:

(0.2.x ivtv driver)
general protection fault: 0000 [#1]
PREEMPT
Modules linked in: tuner tveeprom ivtv tda9887 saa7127 saa7115 msp3400
i2c_algo_bit i2c_core videodev
CPU: 0
EIP: 0061:[<d09ec891>] Not tainted VLI
EFLAGS: 00010202 (2.6.12-xen0)
EIP is at ivtv_sched_DMA+0x751/0xbe0 [ivtv]
eax: 00000003 ebx: ffffaff6 ecx: cfd1e000 edx: 00000000
esi: d0a05520 edi: 00000202 ebp: c9a77ed8 esp: c9a77e70
ds: 007b es: 007b ss: 0069
Process ivtv-enc (pid: 4108, threadinfo=c9a76000 task=ca6d15d0)
Stack: d09c0004 cec609e0 c9a77ed8 000217c0 c036bee0 00000001 00000001
00000000
0000006c cfd1e02c 00000001 00000000 00000000 00024000 000217c0
00000000
cfd1e000 00000000 00000000 00000000 00000000 00000000 000ffb1c
00000000
Call Trace:
[<c01187b0>] default_wake_function+0x0/0x20
[<c01187b0>] default_wake_function+0x0/0x20
[<c0117b0c>] recalc_task_prio+0x8c/0x160
[<d09efa28>] enc_work_handler+0x88/0x90 [ivtv]
[<d09f122d>] ivtv_enc_thread+0x16d/0x1de [ivtv]
[<c0132b10>] autoremove_wake_function+0x0/0x60
[<c0109802>] ret_from_fork+0x6/0x1c
[<c0132b10>] autoremove_wake_function+0x0/0x60
[<d09f10c0>] ivtv_enc_thread+0x0/0x1de [ivtv]
[<c0107765>] kernel_thread_helper+0x5/0x10
Code: 4b 2d c0 29 d8 3d b8 0b 00 00 76 c9 f6 05 10 40 a0 d0 01 0f 85 50 04
00 00 c7 44 24 04 01 00 00 00 89 34 24 e8 c1 c3 00 00 9c 5f <fa> bb 00 e0
ff ff 21 e3 ff 43 14 8b 86 d4 b0 00 00 8b 4c 24 40
ivtv: ENC: User stopped capture.
ivtv: ENC: DMA still Pending while stoping capture!

(and with 0.3.x driver)
general protection fault: 0000 [#1]
PREEMPT
Modules linked in: tuner tveeprom ivtv tda9887 saa7127 saa7115 msp3400
i2c_algo_bit i2c_core videodev
CPU: 0
EIP: 0061:[<d0a07ad6>] Not tainted VLI
EFLAGS: 00010246 (2.6.12-xen0)
EIP is at dma_from_device+0xb6/0x530 [ivtv]
eax: 00000000 ebx: ffffaf70 ecx: ca437000 edx: 000217c0
esi: 00000246 edi: 00000000 ebp: ca6b0000 esp: c96a9e04
ds: 007b es: 007b ss: 0069
Process ivtv-enc (pid: 4089, threadinfo=c96a8000 task=ca5a90c0)
Stack: d09c0000 cfd0e00a 00000009 00000125 c96a8000 00000000 00000000
cfe4af80
00000087 00000125 c11ff040 c013e0a9 cfe4af7c 00000087 cec68060
ca437000
d0a05818 ca437054 00000000 cfe4aedc ca5aa968 cfe4af7c ca437054
00000005
Call Trace:
[<c013e0a9>] filemap_nopage+0x319/0x3f0
[<d0a05818>] enc_gather_free_buffers+0x88/0x360 [ivtv]
[<d0a07936>] ivtv_sched_DMA+0x886/0x970 [ivtv]
[<c0118949>] __wake_up_sync+0x59/0xa0
[<c01187b0>] default_wake_function+0x0/0x20
[<c02a179a>] schedule+0x6a/0x660
[<c01187b0>] default_wake_function+0x0/0x20
[<d0a0b1b8>] enc_work_handler+0x38/0x40 [ivtv]
[<d0a0c70d>] ivtv_enc_thread+0x16d/0x1e0 [ivtv]
[<c015d782>] filp_close+0x52/0xa0
[<c0132b10>] autoremove_wake_function+0x0/0x60
[<c0109802>] ret_from_fork+0x6/0x1c
[<c0132b10>] autoremove_wake_function+0x0/0x60
[<d0a0c5a0>] ivtv_enc_thread+0x0/0x1e0 [ivtv]
[<c0107765>] kernel_thread_helper+0x5/0x10
Code: 00 e8 3f bf ff ff a1 e0 4b 2d c0 29 d8 3d b8 0b 00 00 76 cc f6 05 48
77 a2 d0 01 74 0c c7 04 24 44 dc a1 d0 e8 ac 4c 71 ef 9c 5e <fa> bb 00 e0
ff ff 21 e3 ff 43 14 8b 85 54 18 00 00 8b 54 24 74
<6>ivtv warning: ENC: DMA still Pending while stopping capture!

In both cases an "dma-part" of the driver is touched. Now, when i
understand it right
(http://lists.xensource.com/archives/html/xen-changelog/2005-07/msg00183.html)
this error shouldn't longer exist but it does, on my system with xen 2.0
testing (which should contain the fix). What could goes wrong?

On http://www.gossamer-threads.com/lists/ivtv/devel/24845 you'll find my
post on ivtv-dev list with a little bit more system informations.

What can i do ?

Manuel


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