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

Re: [Xen-users] Problem with mISDN and HFC-Cards in Asterisk-DomU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Problem with mISDN and HFC-Cards in Asterisk-DomU
From: "sven waeyenbergh" <sven.waeyenbergh@xxxxxxxxx>
Date: Thu, 4 Oct 2007 12:26:59 +0200
Delivery-date: Thu, 04 Oct 2007 03:27:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=06ZtJIYmNjHw5mYWJ2qZLdkpzG8sz0TDHinOyU0HfT4=; b=DyI2XEOJ6LAKkq2Xm+G4NADE4PwTBLlXnjAhUnjycSPbIjx2Uc3YBk211vkPq2QhxHubfJ0/Dc4cfFZ3/NitqP7UQa5UhK5Dbf30UfRlaGjqhN6f2IXhPdTlKr6/ArNDROM0ue4mBYjUqlM9vgFAHMmMv5DlG0z44PWojipVqgo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Q8sZ0Q2kHbmsWXAiHj/PJlz94r4DUmLIT9i6DKkEntG1kTIJiwEhEasyfXHALfD+FH2jvfw5kqdORTE3IyRgRuGudLu2bDdYGg16cu/BJhGoLen7OmGGUoSYlk1aWnt9SrCzbbJAfId9MtFShTTnVJoCHEeS1g/xUIuQDiGLrEM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200710032131.55840.dennis.petschull@xxxxxx>
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>
References: <200710032131.55840.dennis.petschull@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Dennis,

I had similar problems with my ivtv-based TV cards.
Sometimes pci card drivers loaded fine, sometimes not, usually when lots of other domU's were running.

Solution (for me) was to:
-  add the following to the domU config file
   extra = "root=/dev/hda1 iommu=soft swiotlb=force"
- assign at least 312MB to the domU (any lower than that, and the domU became unstable, do not know why)

since i did that, it has been running stable

Hope it helps,
Sven

On 10/3/07, Dennis Petschull <dennis.petschull@xxxxxx > wrote:
Hello,

I am having problems, getting my asterisk-domU to work properly. It consists
of the following components:

- Debian Etch under Xen-3.1 with a 2.6.18-kernel
- Asterisk 1.2.24
- mISDN-1.1.5

I have 2 HFC-ISDN-cards, which I pass through to the Asterisk-DomU in
permissive mode. This is working fine.
The strange problem is, that the two HFC-ISDN-cards are not beeing initialized
by the mISDN-driver if there are more than 3 other domUs up and running.

I get the following error message:
HFC-PCI: Error allocating memory for FIFO!
FATAL: Error inserting hfcpci (/lib/modules/2.6.18-xenU/extra/hfcpci.ko): No
such device

If you look into the mISDN source-code you will find the following snippet of
code in /drivers/isdn/hardware/mISDN/hfc_pci.c, which produces the above
error:

        /* Allocate memory for FIFOS */
        /* the memory needs to be on a 32k boundary within the first 4G */
        pci_set_dma_mask(dev_hfcpci, 0xFFFF8000);
        buffer = pci_alloc_consistent(dev_hfcpci, 0x8000, &hc-> hw.dmahandle);
        /* We silently assume the address is okay if nonzero */
        if(!buffer) {
                printk(KERN_WARNING "HFC-PCI: Error allocating memory for
FIFO!\n");
                return 1;
        }


But what is even more strange is the following:
As far as I can see, mISDN will also not initialize the HFC-cards in the
asterisk domU if I have not started all the other domUs at least once. Than I
have to shut down one of the other domUs, initialize the mISDN drivers, and
restart the other domU again.

Just in case it might help to solve the problem, I will post the output of
lspci -vv in the case where mISDN CAN initialize the cards and in the case
where it CANNOT. Here it comes:

mISDN CAN initialize the cards:

asterisk:~# lspci -vv
01:07.0 Network controller: Cologne Chip Designs GmbH ISDN network controller
[HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 16 (4000ns max)
        Interrupt: pin A routed to IRQ 19
        Region 0: I/O ports at a400 [disabled] [size=8]
        Region 1: Memory at f4004000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME+

01:08.0 Network controller: Cologne Chip Designs GmbH ISDN network controller
[HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 16 (4000ns max)
        Interrupt: pin A routed to IRQ 18
        Region 0: I/O ports at a800 [disabled] [size=8]
        Region 1: Memory at f4005000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME+


mISDN CANNOT initialize the cards:

asterisk:~# lspci -vv
01:07.0 Network controller: Cologne Chip Designs GmbH ISDN network controller
[HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 16 (4000ns max)
        Interrupt: pin A routed to IRQ 19
        Region 0: I/O ports at a400 [size=8]
        Region 1: Memory at f4004000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME+

01:08.0 Network controller: Cologne Chip Designs GmbH ISDN network controller
[HFC-PCI] (rev 02)
        Subsystem: Cologne Chip Designs GmbH ISDN Board
        Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 18
        Region 0: I/O ports at a800 [disabled] [size=8]
        Region 1: Memory at f4005000 (32-bit, non-prefetchable) [disabled]
[size=256]
        Capabilities: [40] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME+


Has anyone ever encountered such a strange problem? Does anyone know how to
solve this problem?

Thanks!

Greetings,
Dennis

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

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