Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 9 Dec 2000 14:47:44 +0100 (MET)
From:      hm@hcs.de (Hellmuth Michaelis)
To:        ISDN Mailinglist <freebsd-isdn@freebsd.org>
Subject:   Re: Troubles with the Winbond PCI ISDN card
Message-ID:  <20001209134744.4A778293@hcswork.hcs.de>
In-Reply-To: <00120201444303.17983@Gandalf.t51b.nordahl.net> "from Frode Nordahl at Dec 2, 2000 01:44:43 am"

next in thread | previous in thread | raw e-mail | index | archive | help

> I also experience problems with an Winbond-based PCI internal TA (Asuscom PCI 
> shit.  If anyone has a ISDN card they are extreemely happy with, please let 
> me know :) )
> 
> The connection frezes now and then without any obvious reason.  Sometimes it 
> may run for hours, other times it takes 10 minutes and it's down.

I couldn't stop thinking about this, so i replaced the ISDN card in my main
gateway last sunday with the Winbond-based Asuscom card.

This gateway machine is connected to my provider and the company i work for
and is moderatly busy in terms of serving ISDN. It uses all forms of callback
and calledback depending on daytime, day of week and from which side a 
connection is established. It uses isp/sppp for one connection and user-ppp
for the other. It now has and uptime of 5 days, 20 hours and handled more
than 1700 ISDN transactions. It hangs on an internal PBX (which handles
my lab ISDN telephony and analog modem traffic) with a firmware (that does
a real clean and reproducible bug-free DSS1 protocol) which i am using now
for several years for internal i4b development purposes.

The machine itself is busy. Its a web server, web cache, mailer, dns-, print-,
cvs-, cvsup- and time server for our home network and it collects weather 
statistics and temperature statistics from various sensors in my house into a
rrd database.

Since the setup last sunday it produced the following (recovered) i4b-based
error messages:

i4b-L2 i4b_rxd_ack: ((N(R)-1)=9) != (UA=10) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=0) != (UA=1) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=1) != (UA=2) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=15) != (UA=16) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=1) != (UA=2) !!!
i4b-L1 iwic_dchan_xirq: XCOL in state F7
i4b-L2 i4b_rxd_ack: ((N(R)-1)=19) != (UA=20) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=7) != (UA=8) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=18) != (UA=19) !!!
i4b-L1 iwic_dchan_xirq: XCOL in state F7
i4b-L2 i4b_rxd_ack: ((N(R)-1)=11) != (UA=12) !!!
i4b-L2 i4b_rxd_ack: ((N(R)-1)=0) != (UA=1) !!!

This is much (about one third or one quarter) less errors (of the same type)
than the Teles S0/16 ISA card produced in roughly the same uptimes before.

It may be that the iwic driver has still bugs (thats very likely) but i 
cannot reproduce and/or confirm that this driver acts buggy in a DSS1
ISDN environment. Anyway, i will leave this card in that machine to 
gain more experience with it.

hellmuth
-- 
Hellmuth Michaelis                                    Tel   +49 40 55 97 47-70
HCS Hanseatischer Computerservice GmbH                Fax   +49 40 55 97 47-77
Oldesloer Strasse 97-99                               Mail  hm [at] hcs.de
D-22457 Hamburg                                       WWW   http://www.hcs.de


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?20001209134744.4A778293>