thr3ads.net - Xen users - [Xen-users] Problem with mISDN and HFC-Cards in Asterisk-DomU [Oct 2007]

If this information is useful, please help other people find it:
Share via:

Dennis Petschull

2007-Oct-03 19:31 UTC

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

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@lists.xensource.com
http://lists.xensource.com/xen-users

sven waeyenbergh

2007-Oct-04 10:26 UTC

head link

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

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@web.de>
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@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

Denny Schierz

2007-Oct-04 20:32 UTC

head link

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

hi Dennis,

Dennis Petschull schrieb:
> Has anyone ever encountered such a strange problem? Does anyone know how to
> solve this problem?
many users from Xen tried to get ISDN Cards working, me too, but we all
hadn''t success. One of the most problems is the timer. ISDN are very,
very critical what has to do with time (in german: zeitkritisch).

Have a look and search google with Xen and ISDN/mISDN and you will find
some threads.

My Idea was also to get Asterisk working in Xen, but i had no luck ...

cu denny

-- 
Stoppt den Überwachungswahn - Stoppt den Schäuble Katalog:
http://www.nopsis.de



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

Dennis Petschull

2007-Oct-06 08:50 UTC

head link

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

Hey!

That worked great! But I had to append dom0_mem=512M to the Dom0 
kernel-bootparameters, also.

Thanks for your help,
Dennis

Am Donnerstag, 4. Oktober 2007 schrieb sven waeyenbergh:> 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@web.de> 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@lists.xensource.com
> > http://lists.xensource.com/xen-users


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

Dennis Petschull

2007-Oct-06 09:23 UTC

head link

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

Hey Denny.

By now, I managed to get the Asterisk-DomU fully working (see other post in 
this thread). I will report back for any problems or difficulties. Wish me 
luck ;-)

Cya,
Dennis

Am Donnerstag, 4. Oktober 2007 schrieb Denny Schierz:> hi Dennis,
>
> Dennis Petschull schrieb:
> > Has anyone ever encountered such a strange problem? Does anyone know
how
> > to solve this problem?
>
> many users from Xen tried to get ISDN Cards working, me too, but we all
> hadn''t success. One of the most problems is the timer. ISDN are
very,
> very critical what has to do with time (in german: zeitkritisch).
>
> Have a look and search google with Xen and ISDN/mISDN and you will find
> some threads.
>
> My Idea was also to get Asterisk working in Xen, but i had no luck ...
>
> cu denny


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

Maybe Matching Threads

Search for more possibly parallel threads

Xen users - Oct 2007 - Problem with mISDN and HFC-Cards in Asterisk-DomU

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

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

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

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

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

Maybe Matching Threads