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-users

[Xen-users] XEN and AVM-Fritzcard in Dom-U

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XEN and AVM-Fritzcard in Dom-U
From: "Rene" <install@xxxxxxxxxxxx>
Date: Fri, 16 Dec 2005 07:34:45 +0100 (CET)
Delivery-date: Fri, 16 Dec 2005 06:36:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.4
Hi list.

I successfully comlied my own Dom0-Kernel with capi-support and use it in
test-domU fot getting my isdn-card to work in it.
I have compiled the driver from ftp.avm.de .
In lspci i can see my card.
I use xen-2.0.7 from source.

If i try to start it i get the following error :

fcpci: module license 'Proprietary' taints kernel.
fcpci: AVM FRITZ!Card PCI driver, revision 0.6.2
fcpci: (fcpci built on Dec 16 2005 at 07:09:12)
PCI: Obtained IRQ 23 for device 0000:02:0b.0
fcpci: AVM FRITZ!Card PCI found: port 0xdf80, irq 23
fcpci: Loading...
fcpci: Driver 'fcpci' attached to stack. (152)
general protection fault: 0000 [#1]
PREEMPT
Modules linked in: fcpci
CPU:    0
EIP:    0061:[<c292c4ab>]    Tainted: P      VLI
EFLAGS: 00010246   (2.6.11.12-xen0-rema)
EIP is at enter_critical+0xb/0x20 [fcpci]
eax: 00000246   ebx: c1972004   ecx: 00001200   edx: c1972004
esi: c2951edc   edi: c0024c00   ebp: c079fe20   esp: c079fe14
ds: 007b   es: 007b   ss: 0069
Process modprobe (pid: 987, threadinfo=c079e000 task=c07aba80)
Stack: c28de18e 00001200 00000000 00000000 c28e1c3f c197201c 000000bf
c28e133e
       c2951edc c1972004 c1fa8a04 c1fa8a58 c28e1ddc c1fec004 000032c8
00000001
       c292c71c c2950e60 c292c562 c1fa8a04 c1fa8a58 c292cc7d c1fa8a04
c2950da0
Call Trace:
 [<c28de18e>] EnterCritical+0xe/0x10 [fcpci]
 [<c28e1c3f>] _LI_AddTop+0xf/0x40 [fcpci]
 [<c28e133e>] QUEUE_Init+0x7e/0x90 [fcpci]
 [<c28e1ddc>] CM_Start+0x3c/0x80 [fcpci]
 [<c292c71c>] start+0x3c/0xc0 [fcpci]
 [<c292c562>] params_ok+0x42/0x60 [fcpci]
 [<c292cc7d>] add_card+0x9d/0x1b0 [fcpci]
 [<c292f16f>] link_library+0xf/0x20 [fcpci]
 [<c292c1ac>] fritz_probe+0x7c/0x130 [fcpci]
 [<c0204ef0>] kobject_hotplug+0x270/0x300
 [<c02108b2>] pci_device_probe_static+0x52/0x70
 [<c021090c>] __pci_device_probe+0x3c/0x50
 [<c021094c>] pci_device_probe+0x2c/0x50
 [<c02316bf>] driver_probe_device+0x2f/0x80
 [<c023180c>] driver_attach+0x5c/0xa0
 [<c0231d5d>] bus_add_driver+0x9d/0xd0
 [<c023237f>] driver_register+0x2f/0x40
 [<c0210bc4>] pci_register_driver+0x64/0x90
 [<c295a0ba>] fritz_init+0xba/0x116 [fcpci]
 [<c01342a3>] sys_init_module+0x183/0x240
 [<c0109268>] syscall_call+0x7/0xb
Code: 0b 01 ca 89 14 24 e8 65 25 fb ff 01 03 8b 5c 24 0c 83 c4 10 c3 8d 74
26 00 8d bc 27 00 00 00 00 a1 d0 7e 95 c2 85 c0 75 08 9c 58 <fa> a3 30 7f
95 c2 ff 05 d0 7e 95 c2 c3 90 8d b4 26 00 00 00 00

can you give me any hints please.

kind regards
rene


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

<Prev in Thread] Current Thread [Next in Thread>