Re: [asterisk-users] Problem installing B410P BRI card for asterisk

2012-02-21 Thread Alec Davis
Marco
 
Did you get to the bottom of this.
 
I've just come across the same problem today also with a B410P after
upgrading from debian lenny( 2.6.26-2-686 ) to squeeze ( 2.6.32-5-686 ).
 
On reboot I often get BUG: soft lockup - CPU#0 stuck for 61s[swapper:0]
The only fix is to power off
 
but here's the clue
Feb 21 21:15:08 astrid kernel: [4.638977] hfc_multi :07:01.0: PCI
INT A - GSI 19 (level, low) - IRQ 19
Feb 21 21:15:08 astrid kernel: [4.638982] Digium Inc. HFC-4S Card:
defined at IOBASE 0xdc00 IRQ 19 HZ 250 leds-type 2
Feb 21 21:15:08 astrid kernel: [4.803576] wcb4xxp :07:01.0: PCI INT
A - GSI 19 (level, low) - IRQ 19
Feb 21 21:15:08 astrid kernel: [4.803607] wcb4xxp :07:01.0:
Identified Wildcard B410P (controller rev 1) at 0001dc00, IRQ 19

hfcmulti can be found here;
/lib/modules/2.6.32-5-686/kernel/drivers/isdn/hardware/mISDN/hfcmulti.ko

I've got the system running at the moment with the previous kernel, so
nothing wrong with the B410P.
 
I'm hoping that 'tomorrow' that adding the line below to
/etc/modprobe.d/blacklist.conf will fix my lockups.
  blacklist hfcmulti
 
Alec Davis
 
 


  _  

From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Marco
Mooijekind
Sent: Friday, 30 December 2011 9:45 p.m.
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Problem installing B410P BRI card for asterisk


Dear all,

I know this is more a Digium hardware than an Asterisk issue. Already posted
a question at Digium, however also like to see whether anyone in the
Asterisk community has encountered the following situation:

I installed a Digium B410P BRI PCI card on my new asterisk server, following
the steps specified in the manual. I can see the PCI card is available using
the lspci command:

...
04:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network
Connection [8086:10d3]
05:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network
Connection [8086:10d3]
08:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge
[1a03:1150] (rev 02)
09:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED
Graphics Family [1a03:2000] (rev 10)
0a:01.0 ISDN controller [0204]: Digium, Inc. Wildcard B410 quad-BRI card
[d161:b410] (rev 01)
...

I specified the following in my system.conf in /etc/dahdi:

loadzone = nl
defaultzone = nl
span = 1,1,0,ccs,ami
bchan = 1,2
hardhdlc = 3

I loaded the driver using sudo modprobe wcb4xxp.
Next I ran dahdi_cfg -vv which returns:

DAHDI Tools Version - 2.5.0.2

DAHDI Version: 2.5.0.2
Echo Canceller(s): HWEC
Configuration
==

SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Echo Canceler: none) (Slaves: 01)
Channel 02: Clear channel (Default) (Echo Canceler: none) (Slaves: 02)
Channel 03: Hardware assisted D-channel (Default) (Echo Canceler: none)
(Slaves: 03)

3 channels to configure.

DAHDI_SPANCONFIG failed on span 1: No such device or address (6)

I'm in doubt about the DAHDI_SPANCONFIG failed on span 1: No such device or
address (6).
Next, if i execute sudo dmesg as specified by the manual it returns a huge
trace:


[  376.082907] Wrote 0x0 to register 0x1ab but got back 0x4
[  376.594754] Wrote 0x0 to register 0x1ab but got back 0x4
[  377.106605] Wrote 0x0 to register 0x1ab but got back 0x4
[  377.618423] Wrote 0x0 to register 0x1ab but got back 0x4
[  378.130266] Wrote 0x0 to register 0x1ab but got back 0x4
[  378.642088] Wrote 0x0 to register 0x1ab but got back 0x4
[ 1202.812870] show_signal_msg: 21 callbacks suppressed
[ 1202.812876] dahdi_tool[1277]: segfault at 3fc378fa0 ip 004021ac
sp 7fff131dd930 error 4 in dahdi_tool[40+3000]

And a lot of Wrote 0x0 to register 0x1ab but got back 0x4 statements.

If i run dahdi_tools it fails with a segmentation fault.

Any suggestions are appreciated!

Kind regards,

Marco Mooijekind.



--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] Problem installing B410P BRI card for asterisk

2011-12-30 Thread Marco Mooijekind
Dear all,

I know this is more a Digium hardware than an Asterisk issue. Already
posted a question at Digium, however also like to see whether anyone in the
Asterisk community has encountered the following situation:

I installed a Digium B410P BRI PCI card on my new asterisk server,
following the steps specified in the manual. I can see the PCI card is
available using the lspci command:

...
04:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
05:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
08:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI
Bridge [1a03:1150] (rev 02)
09:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED
Graphics Family [1a03:2000] (rev 10)
0a:01.0 ISDN controller [0204]: Digium, Inc. Wildcard B410 quad-BRI card
[d161:b410] (rev 01)
...

I specified the following in my system.conf in /etc/dahdi:

loadzone = nl
defaultzone = nl
span = 1,1,0,ccs,ami
bchan = 1,2
hardhdlc = 3

I loaded the driver using sudo modprobe wcb4xxp.
Next I ran dahdi_cfg -vv which returns:

DAHDI Tools Version - 2.5.0.2

DAHDI Version: 2.5.0.2
Echo Canceller(s): HWEC
Configuration
==

SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Echo Canceler: none) (Slaves: 01)
Channel 02: Clear channel (Default) (Echo Canceler: none) (Slaves: 02)
Channel 03: Hardware assisted D-channel (Default) (Echo Canceler: none)
(Slaves: 03)

3 channels to configure.

DAHDI_SPANCONFIG failed on span 1: No such device or address (6)

I'm in doubt about the DAHDI_SPANCONFIG failed on span 1: No such device
or address (6).
Next, if i execute sudo dmesg as specified by the manual it returns a huge
trace:


[  376.082907] Wrote 0x0 to register 0x1ab but got back 0x4
[  376.594754] Wrote 0x0 to register 0x1ab but got back 0x4
[  377.106605] Wrote 0x0 to register 0x1ab but got back 0x4
[  377.618423] Wrote 0x0 to register 0x1ab but got back 0x4
[  378.130266] Wrote 0x0 to register 0x1ab but got back 0x4
[  378.642088] Wrote 0x0 to register 0x1ab but got back 0x4
[ 1202.812870] show_signal_msg: 21 callbacks suppressed
[ 1202.812876] dahdi_tool[1277]: segfault at 3fc378fa0 ip 004021ac
sp 7fff131dd930 error 4 in dahdi_tool[40+3000]

And a lot of Wrote 0x0 to register 0x1ab but got back 0x4 statements.

If i run dahdi_tools it fails with a segmentation fault.

Any suggestions are appreciated!

Kind regards,

Marco Mooijekind.
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Problem installing B410P BRI card for asterisk

2011-12-30 Thread Kevin P. Fleming

On 12/30/2011 02:44 AM, Marco Mooijekind wrote:

Dear all,

I know this is more a Digium hardware than an Asterisk issue. Already
posted a question at Digium, however also like to see whether anyone in
the Asterisk community has encountered the following situation:

I installed a Digium B410P BRI PCI card on my new asterisk server,
following the steps specified in the manual. I can see the PCI card is
available using the lspci command:

...
04:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
05:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
08:00.0 PCI bridge [0604]: ASPEED Technology, Inc. AST1150 PCI-to-PCI
Bridge [1a03:1150] (rev 02)
09:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED
Graphics Family [1a03:2000] (rev 10)
0a:01.0 ISDN controller [0204]: Digium, Inc. Wildcard B410 quad-BRI card
[d161:b410] (rev 01)
...

I specified the following in my system.conf in /etc/dahdi:

loadzone = nl
defaultzone = nl
span = 1,1,0,ccs,ami
bchan = 1,2
hardhdlc = 3

I loaded the driver using sudo modprobe wcb4xxp.
Next I ran dahdi_cfg -vv which returns:

DAHDI Tools Version - 2.5.0.2

DAHDI Version: 2.5.0.2
Echo Canceller(s): HWEC
Configuration
==

SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Echo Canceler: none) (Slaves: 01)
Channel 02: Clear channel (Default) (Echo Canceler: none) (Slaves: 02)
Channel 03: Hardware assisted D-channel (Default) (Echo Canceler: none)
(Slaves: 03)

3 channels to configure.

DAHDI_SPANCONFIG failed on span 1: No such device or address (6)

I'm in doubt about the DAHDI_SPANCONFIG failed on span 1: No such
device or address (6).
Next, if i execute sudo dmesg as specified by the manual it returns a
huge trace:


[  376.082907] Wrote 0x0 to register 0x1ab but got back 0x4
[  376.594754] Wrote 0x0 to register 0x1ab but got back 0x4
[  377.106605] Wrote 0x0 to register 0x1ab but got back 0x4
[  377.618423] Wrote 0x0 to register 0x1ab but got back 0x4
[  378.130266] Wrote 0x0 to register 0x1ab but got back 0x4
[  378.642088] Wrote 0x0 to register 0x1ab but got back 0x4
[ 1202.812870] show_signal_msg: 21 callbacks suppressed
[ 1202.812876] dahdi_tool[1277]: segfault at 3fc378fa0 ip
004021ac sp 7fff131dd930 error 4 in dahdi_tool[40+3000]

And a lot of Wrote 0x0 to register 0x1ab but got back 0x4 statements.

If i run dahdi_tools it fails with a segmentation fault.

Any suggestions are appreciated!


Either your B410P card is misbehaving (i.e. broken), or there is some 
sort of PCI compatibility issue between it and the system you have it 
installed in. This is a hardware issue, and should be pursed with Digium 
Support.


--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kflem...@digium.com | SIP: kpflem...@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com  www.asterisk.org

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] Problem with B410P

2008-04-16 Thread Y BAESA
Hello, 
Let me ask for help on a problem 
That I can not solve a 

2 B410P on my server 
I can not mounted ports TE UP 
Everything seems to have been successfully compile no apparent errors 

Misdn (1_1_7_2 version) 
Zaptel (version 1.4.9.2) 
Asterisk (version 1.4.18) 
Kernel (version 2.6.17-5mdv) 

Misdn-init scan 
Card=1.0x4
Card=2.0x4

MISDN scan 
BN4S0 
BN4S0 

Extract from misdn.log 

Tue Apr 15 14:39:34 2008: P [0] - mISDN Channel Driver Registered -- 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [1] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [2] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [3] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [4] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [5] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [6] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [7] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:34 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:34 2008: P [8] MGMT: SSTATUS: L2_RELEASED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
Tue Apr 15 14:39:41 2008: P [0] MGMT: SSTATUS: L1_DEACTIVATED 
# 
Test call 
# 
Tue Apr 15 14:40:22 2008: P [0] Checking Port: 0 
Tue Apr 15 14:40:22 2008: P [0] - Group Call group: first_extern 
Tue Apr 15 14:40:22 2008: P Group [1] [first_extern] Port [1] 
Tue Apr 15 14:40:22 2008: P [1] PMP down Port 
Tue Apr 15 14:40:22 2008: P [1] portup: 0 
Tue Apr 15 14:40:22 2008: P Group [2] [first_extern] Port [2] 
Tue Apr 15 14:40:22 2008: P [2] PMP down Port 
Tue Apr 15 14:40:22 2008: P [2] portup: 0 
Tue Apr 15 14:40:22 2008: P Group [3] [first_extern] Port [3] 
Tue Apr 15 14:40:22 2008: P [3] Port down PMP 
Tue Apr 15 14:40:22 2008: P [3] portup: 0 
Tue Apr 15 14:40:22 2008: P Group [4] [first_extern] Port [4] 
Tue Apr 15 14:40:22 2008: P [4] PMP down Port 
Tue Apr 15 14:40:22 2008: P [4] portup: 0 
Tue Apr 15 14:40:22 2008: P [5] Group [first_extern] Port [5] 
Tue Apr 15 14:40:22 2008: P [5] PMP down Port 
Tue Apr 15 14:40:22 2008: P [5] portup: 0 
Tue Apr 15 14:40:22 2008: P [6] Group [first_extern] Port [6] 
Tue Apr 15 14:40:22 2008: P [6] Port down PMP 
Tue Apr 15 14:40:22 2008: P [6] portup: 0 
Tue Apr 15 14:40:22 2008: P [7] Group [first_extern] Port [7] 
Tue Apr 15 14:40:22 2008: P [7] PMP down Port 
Tue Apr 15 14:40:22 2008: P [7] portup: 0 
Tue Apr 15 14:40:22 2008: P [8] Group [first_extern] Port [8] 
Tue Apr 15 14:40:22 2008: P [8] PMP down Port 
Tue Apr 15 14:40:22 2008: P [8] portup: 0 


Asterisk log extract 

P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 
P [0] MGMT: SSTATUS: L1_DEACTIVATED 

* CLI misdn show stacks 
BEGIN: STACK_LIST 
   * Type 1 TE Prot. PMP L2Link DOWN L1Link: DOWN Bloked: 0 Debug: 4 
   * Type 2 TE Prot. PMP L2Link DOWN L1Link: DOWN Bloked: 0 Debug: 4 
   * Type 3 TE Prot. PMP L2Link DOWN L1Link: DOWN Bloked: 0 Debug: 4 
   * Type 4 TE Prot. PMP L2Link DOWN L1Link: DOWN Bloked: 0 Debug: 4 
So  

Do you have an idea 

With my thanks 
Yves


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Problem with B410P

2008-04-16 Thread Ex Vito
  Could be this...
  
http://www.misdn.org/index.php/FAQ_chan_mISDN#Why_does_the_L1_goes_DOWN_on_my_PMP_Isdn_Link.3F_Or_why_do_i_get_No_free_chan_even_after_group_call_from_chan_misdn_if_dialing_out_on_my_PMP_Link.3F

  Hmmm... that's a long link. It is the
  Why does the L1 goes DOWN on my PMP Isdn Link FAQ in the
  chan_misdn FAQ at http://www.misdn.org/index.php/FAQ_chan_mISDN

  In short, the telcos shut PMP links down to save on power costs, you
  need to bring them up before initiating an outbound call.

  Cheers,
--
 exvito

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Problem with B410P

2008-04-16 Thread Y BAESA
Re, 
That is correct, in the case of France Telecom 

Pb resolved. 
With my thanks 

A + 
Yves

Le mercredi 16 avril 2008 à 14:45 +0100, Ex Vito a écrit :
 Could be this...
   
 http://www.misdn.org/index.php/FAQ_chan_mISDN#Why_does_the_L1_goes_DOWN_on_my_PMP_Isdn_Link.3F_Or_why_do_i_get_No_free_chan_even_after_group_call_from_chan_misdn_if_dialing_out_on_my_PMP_Link.3F
 
   Hmmm... that's a long link. It is the
   Why does the L1 goes DOWN on my PMP Isdn Link FAQ in the
   chan_misdn FAQ at http://www.misdn.org/index.php/FAQ_chan_mISDN
 
   In short, the telcos shut PMP links down to save on power costs, you
   need to bring them up before initiating an outbound call.
 
   Cheers,
 --
  exvito
 
 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
 


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users