From owner-freebsd-isdn Mon Aug 16 14:30:41 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 5C7EA1550B for ; Mon, 16 Aug 1999 14:30:27 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id XAA09070; Mon, 16 Aug 1999 23:20:15 +0200 (CEST) Message-Id: <199908162120.XAA09070@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Gaertner Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: error messages Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 15 Aug 1999 20:04:40 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Aug 1999 23:20:14 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andreas Gaertner writes: > >hi, > >recently i encountered the following error messages while transferring >around a couple of megabytes to the other peer. this occurred all of a >sudden and unforced. what do they mean? > >Aug 15 15:49:41 sun /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) >+ k) & > 127)! >Aug 15 15:49:41 sun /kernel: i4b-L2-i4b_i_frame_queued_up: state = >ST_MULTIFR >Aug 15 15:49:41 sun /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=6, V(S)=7, >V(A)= >6,ACKP=0,PBSY=0,OBSY=0 >Aug 15 15:49:46 sun /kernel: i4b-L3-i4b_decode_q931: cannot find >calldescriptor >for cr = 0xc, crflag = 0x1, msg = 0x4d, frame = 0x4d 0x1c 0x17 0x91 0xa1 >0x14 0 >x2 0x1 0x75 0x2 0x1 0x24 0x30 0xc 0x30 0xa 0xa1 0x5 0x30 0x3 0x2 0x1 0x0 >0x82 0x >1 0x0 >Aug 15 15:50:40 sun /kernel: i4b-L3-T310_timeout: CALL PROC timeout, cr = >12 >Aug 15 15:50:40 sun /kernel: i4b-L3-next_l3state: FSM illegal state, state >= ST_ >U0 - Null, event = EV_T310EXP - T310 timeout! >Aug 15 15:51:37 sun /kernel: isp0: Down event, taking interface down. >Aug 15 15:51:41 sun /kernel: i4b-L3-i4b_decode_q931: cannot find >calldescriptor >for cr = 0x41, crflag = 0x0, msg = 0x4d, frame = 0x4d 0x8 0x2 0x85 0x90 > >thanks in advance for any help, kind regards, > this was fixed long ago by Hellmuth (with a little help from his friends :) which version of isdn4bsd are you using ? --- 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