Date: Mon, 20 Sep 1999 23:33:11 +0200 From: Gary Jennejohn <garyj@peedub.muc.de> To: Luke Roberts <luke@roberts.nl> Cc: freebsd-isdn@freebsd.org Subject: Re: 14b L2 and L3 errors Message-ID: <199909202133.XAA47266@peedub.muc.de> In-Reply-To: Your message of "Mon, 20 Sep 1999 14:00:41 %2B0200." <4.2.0.58.19990920140034.009b61d0@pop.roberts.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Luke Roberts writes: >Hi, > >I'mn running i4b version 00.82.0 on FreeBSD 3.2-release on a 300 MHz K6-2 >machine with 64 MB SDRAM and a Teles 16.3 ISA non plug n play card. > [snip] > >The FreeBSD machine gives the following error codes: > >14b-L2-i4b_T200_timeout: unit 0, RC = 0 >Sep 20 10:49:53 dilis /kernel: 14b-L2-i4b_T200_timeout: unit 0, RC = 0 >Sep 20 10:49:53 dilis /kernel: 14b-L2-i4b_T200_timeout: unit 0, RC = 0 >14b-L3-T305_timeout: DISC not answered, cr = 80 >Sep 20 10:50:24 dilis /kernel: 14b-L3-T305_timeout: DISC not answered, cr = 80 >Sep 20 10:50:24 dilis /kernel: 14b-L3-T305_timeout: DISC not answered, cr = 80 >14b-L3-T308_timeout: REL not answered, cr = 80 >Sep 20 10:50:28 dilis /kernel: 14b-L3-T308_timeout: REL not answered, cr = 80 >Sep 20 10:50:28 dilis /kernel: 14b-L3-T308_timeout: REL not answered, cr = 80 >14b-L3-T303_timeout: SETUP not answered, cr = 94 >14b-L3-T303_next_l3state: FSM illegal sate, state = ST_OW - Out Wait EST, >event = EV_T303EXP - T303 timeout! >Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_timeout: SETUP not answered, cr = 9 >4 >Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_timeout: SETUP not answered, cr = 9 >4 >Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_next_l3state: FSM illegal sate, >state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! >Sep 20 10:50:35 dilis /kernel: 14b-L3-T303_next_l3state: FSM illegal sate, >state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! > [snip] funny, no one else has reported a problem like this with the 16.3. this doesn't answer your question, but this problem sure looks a lot like a bug which I (and others) thought was limited to the Fritz!Card PCI. It manifests itself in a similar manner - the ISAC just seems to stop working (but only with sPPP). Of course, that means that all communication with the NT also stops, which is basically what you are experiencing. Strangely, this problem has disappeared with -current. However, the trace which you've posted is not enough to even begin to track down the problem. >Also a question? Is anybody working on multichannel ppp? > Brian "Awfulhak" Somers, who maintains the user-land PPP stuff, has modified it so that it can work with i4b. Since the user-land PPP supports MPPP, this means that i4b also can. This stuff is part of 0.83 and also in -current. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com 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?199909202133.XAA47266>