Date: Sat, 2 Dec 2000 01:44:43 +0100 From: Frode Nordahl <frode@nordahl.net> To: hm@hcs.de (Hellmuth Michaelis) Cc: freebsd-isdn@freebsd.org Subject: Re: Troubles with the Winbond PCI ISDN card Message-ID: <00120201444303.17983@Gandalf.t51b.nordahl.net>
next in thread | raw e-mail | index | archive | help
Hello, 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. The connection seems to be open, but no data is passed back or forth. /var/log/messages contains alot of the messages shown below before the freze occurs. (About a minute or so with messages like this) Dec 2 01:17:33 Gandalf /kernel: isp0: invalid input packet <addr=0xc3 ctrl=0x9c proto=0xb048> Dec 2 01:17:33 Gandalf /kernel: isp0: invalid input packet <addr=0xc3 ctrl=0xff proto=0x3d2f> Dec 2 01:17:33 Gandalf /kernel: isp0: invalid input packet <addr=0xb2 ctrl=0x2b proto=0xcd19> Dec 2 01:17:33 Gandalf /kernel: isp0: invalid input packet <addr=0x9 ctrl=0xe proto=0xb98> --- Etc. (mail me if you want the full output.) Do you have any idea what makes this happen? What is the development status for the iwic driver? Any sollutions/workarounds? -- Mvh, Frode Nordahl From the keyboard of Vittorio Mori: > > i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 > > i4b: unit 0, assigned TEI = 81 = 0x51 > > i4b: unit 0, assigned TEI = 81 = 0x51 > > i4b-L3 T310_timeout: CALL PROC timeout, cr = 70 > > i4b-L2 i4b_ph_data_ind: ERROR, S-frame < 6 octetts! I have never seen this before. The layer 2 seems to get erroneous data from the wire which has the effect of irritating the D-channel communication. It has nothing to do with the choice between user ppp and sppp because both are not involved in this. They operate on the B-channel whereas your primary problem is the D-channel (call control channel). The thing which irritates me is that it does not happen as soon as the first call is made. It might be your hardware or your NT or your card or a bug in i4b or a bug in your PBX and/or exchange office. > I alsto tried to put my old ISA USR TA int into the machine, but I can't > make it work on 4.2-STABLE, the compiled kernel coredumps on load (!) ... it > seems the kernel is not getting the right ISA base adress (which is default, > 0x268) I have it working under FreeBSD 4.1.1-STABLE with i4b 0.96: isic0 at port 0x8268,0x268-0x26f,0x668-0x66f,0xa68-0xa6f,0xe68-0xe6f,0x1268-0x12 ,0xe668-0xe66f,0xea68-0xea6f,0xee68-0xee6f,0xf268-0xf2 6f,0xf668-0xf66f,0xfa68-0xfa6f,0xfe68-0xfe6f irq 5 flags 0x7 on isa0 isic0: passive stack unit 0 isic0: USRobotics Sportster ISDN TA intern isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) isic0: HSCX 82525 or 21525 Version 2.1 where it runs fine without any noticable problems. 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?00120201444303.17983>