From owner-freebsd-isdn Sat Oct 30 14:22:12 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from bw85zhb.bluewin.ch (bw85zhb.bluewin.ch [195.186.1.75]) by hub.freebsd.org (Postfix) with ESMTP id EA80F14CA2 for ; Sat, 30 Oct 1999 14:22:07 -0700 (PDT) (envelope-from finesse@bluewin.de) Received: from loch.sexy ([195.226.102.69]) by bw85zhb.bluewin.ch ( with ESMTP id AAA577E for ; Sat, 30 Oct 1999 23:22:05 +0200 Received: from finesse.sexy ([192.168.1.4] helo=finesse ident=exim) by loch.sexy with esmtp (Exim 3.02 #1) id 11hfwa-00006N-00 for freebsd-isdn@freebsd.org; Sat, 30 Oct 1999 23:21:48 +0200 Received: from pascal by finesse with local (Exim 3.02 #1) id 11hfwY-00009D-00 for freebsd-isdn@freebsd.org; Sat, 30 Oct 1999 23:21:46 +0200 Date: Sat, 30 Oct 1999 23:21:46 +0200 From: Pascal Gienger To: freebsd-isdn@freebsd.org Subject: MDL-Errors occuring very frequently with i4b-0.83 Message-ID: <19991030232146.A540@finesse.sexy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since two weeks ago, often these error messages appear on my isdn-log, resulting in completely blocking all isdn activity of i4b: Oct 22 22:09:45 loch /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Oct 22 22:09:46 loch /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Oct 22 22:09:47 loch /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Oct 22 22:09:48 loch /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME A closer look reveals this: Oct 29 19:09:30 loch /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated Oct 29 19:09:33 loch last message repeated 3 times Oct 29 19:09:33 loch /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Oct 29 19:09:33 loch /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME [...] I did nothing with the wiring of my S0 bus and I don't see errors on my S0 phone connected to the same bus. Is the NTBA faulty? There are another bunch of "strange" errors never occured before, also resulting in a complete block of all isdn activity: Oct 26 20:01:31 loch isdnd[63]: DBG decr_free_channels: ctrl 0, now 1 chan free Oct 26 20:01:31 loch isdnd[63]: CHD 00057 BlueWindow dialing out from 52739 to 010230191888 Oct 26 20:01:31 loch natd[274]: failed to write packet back (Can't assign requested address) Oct 26 20:01:35 loch /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 68 Or this one: Oct 29 19:10:15 loch /kernel: i4b-L3-T305_timeout: DISC not answered, cr = 103 Oct 29 19:10:19 loch /kernel: i4b-L3-T308_timeout: REL not answered, cr = 103 May it be Telekom's fault or is perhaps my isdn card broken? Does anybody from you had also these error messages and what means "MDL"? How can I find out if it is a problem between Kernel<->Card, Card<->S0 or S0<->Telekom? Do you know any pointers on the net? Pascal -- Unix, Pascal Gienger, Steinstr. 21 /\ 12 .rtsnietS ,regneiG lacsaP xinU Networx 78467 Konstanz / \ znatsnoK 76487 xrowteN & WWW finesse@bluewin.de / \ ed.niweulb@essenif WWW & T: +49 7531 52709, F: 52739 / \ 93725 :F ,90725 1357 94+ :T To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message