Date: Sun, 5 Apr 1998 20:07:03 +0200 (CEST) From: hm@kts.org (Hellmuth Michaelis) To: p@znet.de (Pascal Gienger) Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: unitlengthsrc=rates ignored? and: Problems with "FSM illegal state". Message-ID: <m0yLtot-00024UC@bert.kts.org> In-Reply-To: <19980404142106.30341@magnus.factum-data.de> from Pascal Gienger at "Apr 4, 98 02:21:06 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Pascal Gienger wrote:
> Ich habe 2 Probleme mit i4b 00.51:
>
> 1.)
> I am a subscriber of AOCD information. But due to the many special tariffs
> of Deutsche Telekom, they are getting less useful. At weekends, I have the
> "CityWeekend" tariff giving me 240 seconds-units during Saturday and
> Sunday.
> So i changed "isdnd.rates" (ra0, day 0 and 6 with 240secs in the period
> 00-24) and I changed the unitlenghtsrc in isdnd.rc to
> unitlenghtsrc = rates
>
> Now, after successfully establishing a connection, isdnd reports that
> it will use 240 seconds/unit. Fine.... until the first AOCD accounting
> packet arrives. :( This overrides isdnd's mechanism as if I typed
> "unitlengthsrc = aocd". So I would consider this a bug. ;-) If I put
> "unitlengthsrc = rates" in my isdnd.rc, I want isdnd to take his info from
> isdnd.rates, and not from AOCD. ;-))
Shorthold based on AOCD is currently not fully implemented in isdnd.
Anyway, in case it were already fully implemented, it would still say
what it will use based on the rates file, because you know the unitlength
not before the second AOCD frame, so what do you do for the first unit ?
Right, a good guess :-)
> After some connections and disconnections, I am not able any more to
> hangup manually a connection. isdnd reports a line like this:
>
> Apr 3 13:51:06 finesse isdnd[2573]: ERR FSM ILLEGAL STATE [disconnect-req: \
> idle => Illegal State]
This seems to be a bug in isdnd!
> The problem of missed interrupts and buffer overruns while receiving data
> is still there. In i4b 00.42 I got many messages saying
>
> Mar 2 23:44:02 finesse /kernel: i4b-L1-isic_hscx_irq: RAWHDLC rx buffer \
> overflow in RPF, in_len=2048
>
> It always appeared when swichting fastly between virtual syscons consoles.
>
> Now with i4b 00.51 it doesn't appear any more, but the effects are remaining
> the same. TCP/IP packets are missed and the connection does not transfer any
> data for 2 oder 3 seconds.
> Is a 486DX33 perhaps too slow to answer all the generated interrupts?
It _should_ be ok but currently there are problems in i4b's interrupt handling.
I don't know how long syscons blocks IRQs when switching screens, but i don't
see the problem on a 486/66, i4b even ran tests on a 386/20 here without any
noticable problems; i'm using pcvt everywhere, obviously.
hellmuth
--
Hellmuth Michaelis hm@kts.org Hamburg, Europe
"Those who can, do. Those who can't, talk.
And those who can't talk, talk about talking." (B. Shaw)
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?m0yLtot-00024UC>