Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Sep 1999 07:46:33 +0200 (CEST)
From:      mranner@netway.at
To:        Gary Jennejohn <garyj@muc.de>
Cc:        freebsd-isdn@FreeBSD.ORG, Luke Roberts <luke@roberts.nl>
Subject:   Re: 14b L2 and L3 errors
Message-ID:  <XFMail.990922074633.mranner@netway.at>
In-Reply-To: <199909202133.XAA47266@peedub.muc.de>

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

On 20-Sep-99 Gary Jennejohn wrote:
> 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.
> 

I have exact the same problem with Fritz! PCI. Sometimes 2 times on a day and
sometimes 1 time in a week!

The only solution is to reboot the system (FreeBSD-3.2 Release i4b 0.82.0)

I've tried to upgrade to 0.83.0 but have problems with it! more about this will follow.

cu

/\/\ichael Ranner - Michael Ranner <Michael.Ranner@netway.at>
Michael.Ranner@netway.at - webmaster@mariazell.org
----------------------------------------------------------------------
        Homepage: http://www.netlounge.at/mranner/
Mariazell Online: http://www.mariazell.at/
----------------------------------------------------------------------

What this country needs is a good five cent microcomputer.



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?XFMail.990922074633.mranner>