From owner-freebsd-isdn Sun Jan 14 1:30:43 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 8D69537B698 for ; Sun, 14 Jan 2001 01:30:24 -0800 (PST) Received: from localhost (2274 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Sun, 14 Jan 2001 10:30:14 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #18 built 2000-Oct-9) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id D769452A43; Sun, 14 Jan 2001 10:17:41 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 666A19B1C; Sun, 14 Jan 2001 10:17:41 +0100 (CET) Subject: Re: Winbond chip (W6692CF)ISDN problems In-Reply-To: <3A60EA32.F9CC5384@jak.nl> from Arjan Knepper at "Jan 14, 2001 0:52:18 am" To: arjan@jak.nl (Arjan Knepper) Date: Sun, 14 Jan 2001 10:17:41 +0100 (CET) Cc: freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1335 Message-Id: <20010114091741.666A19B1C@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Arjan Knepper wrote: > > > I installed the newest version of i4b on a FreeBSD 4.1 release, > > > configured and recompiled the kernel without any problems. But the new > > > ISDN enabled kernel reports several errors and warnings: > > > > > > 1.) i4b-L1 dchan_receive : bad read status 0xb0 > > > 2.) i4b-L2 i4b_ph_data_ind : ERROR, I-frame < 6 octets! > > > 3.) i4b-L2 i4b_rxd_u_frame : not mine - UNKNOWN TYPE ERROR, sapi =32, > > > tei=0 frame= 0x81 0x1 0x17 0x0 Oh, oh. "bad read status 0xb0" meand that a CRC error and a receive message aborted condition was detected on the D-channel. The _really_ bad thing about this is that error recovery is equal to zero for this condition in the iwic driver. Frames with CRC errors must be ignored and some chip dependent error recovery procedures must be initiated both of which do not occur. This causes the other layer 2 messages to occur. This is definitely a driver problem, if someone wants to look at this before i have time to do so, the message is generated in i4b_iwic_dchan.c ~line 373. A datasheet for the chip is available from http://www.winbond.com. Now i know why i couldnīt reproduce it here ;-) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message