Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Jan 2001 20:28:38 -0200
From:      Sergio de Souza Prallon <prallon@tmp.com.br>
To:        Andrey Lakhno <land@dnepr.net>
Cc:        freebsd-isdn@freebsd.org
Subject:   Re: 2 Teles PCI cards in one PC
Message-ID:  <20010103202838.A26571@tmp.com.br>
In-Reply-To: <20010103231021.A27703@dnepr.net>; from land@dnepr.net on Wed, Jan 03, 2001 at 11:10:21PM %2B0200
References:  <20010102093844.A10729@dnepr.net> <20010102085741.ED8243A1@hcswork.hcs.de> <20010102110719.A829@dnepr.net> <20010102151432.A21821@tmp.com.br> <20010103002019.A11223@dnepr.net> <20010103150832.A19526@tmp.com.br> <20010103231021.A27703@dnepr.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 03, 2001 at 11:10:21PM +0200, Andrey Lakhno wrote:
> Hi Sergio!
> 
> I need load balancing with 4 B-channels. So I'll use userland ppp.
> 
[...]
> It seems it works. At least computer doesn't reboots.
> Tomorrow I'll try to test it with 2 ISDN lines. Only one line available now.
> 

Cool! That will be a good test for the driver.

> In logs I noticed strange messages:
> 
> Jan  3 22:54:07 <kern.crit> radi /kernel: i4b-L2 F_ILL: FSM function F_ILL execu
> ting
> Jan  3 22:54:07 <kern.crit> radi /kernel: i4b-L2 i4b_next_l2state: FSM illegal s
> tate, state = ST_EST_AW_TEI, event = EV_DLESTRQ!
> Jan  3 22:54:07 <kern.info> radi /kernel: i4b: unit 1, assigned TEI = 92 = 0x5c
> Jan  3 22:54:14 <kern.crit> radi /kernel: i4b-L2 i4b_rxd_ack: ((N(R)-1)=6) != (U
> A=7) !!!
> Jan  3 22:56:59 <kern.crit> radi /kernel: i4b-L2 i4b_rxd_ack: ((N(R)-1)=12) != (
> UA=13) !!!
> 101032257
> Jan  3 22:57:07 <kern.crit> radi /kernel: i4b-L1 itjc_dma_rx_intr: CRC (crc=0x00
> 97, len=322, unit=0)
> 
> Is this error indication ?
> 

Looks like a physical problem (cables, termination).
It can also be related to a problem that occurs on my machine:
on almost every connection establishment I get a "i4b-L2 T200_timeout"
or a "i4b-L2 T202_timeout". After that things goes just fine. It doesn't
occurs on a friend's box that is also helping me debug the driver. For
now I don't have a clue for what it can be. Isdntrace gives even stranger
results, because I see the INFO and IND messages coming from the interrupt
handler saying the connection is active well before (a second o so) the
timeout message. If I use the userland PPP (I normally use the kernel one),
after a dial command, I get the timeout message and for the PPP point of
view, the connection fails. But if I look at the `isdnd -f' VTY, I see
the connection is active. It shows up on the hangup menu and times out
normally if left idle for a long period. If I dial again, the connection
is established and uses the SAME controller/B-channel pair.

Any pointers on this subject anyone can give me will be greatly appreciated.
I have a reasonable experience with networks and some on protocol
implementation but I never read any of the ISDN specs so I don't know what
FSM event or message is missing.

[]'s

--
Prallon


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010103202838.A26571>