Date: Sat, 17 Jul 1999 16:45:44 +0200 From: Christoph Splittgerber <chris@sdata.de> To: freebsd-isdn@FreeBSD.ORG Subject: sporadic hangs Message-ID: <37909718.D4EF80D7@sdata.de>
next in thread | raw e-mail | index | archive | help
Hallo, from time to time (abt. once a week) I see sporadic hangs of the ISDN system (still at 00.70.0) on a FreeBSD 3.2-stable :-(. As I am not into the ISDN code, I have to admit, the error messages don't tell me too much: Jul 17 07:49:43 orion /kernel: i4b: unit 0, assigned TEI = 65 = 0x41 Jul 17 13:04:49 orion /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! Jul 17 13:04:49 orion /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR Jul 17 13:04:49 orion /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=13, V(S)=14, V(A)=13,ACKP=0,PBSY=0,OBSY=0 Jul 17 13:06:06 orion /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x7b, crflag = 0x1, msg = 0x 4d, frame = 0x4d 0x8 0x2 0x81 0x90 Jul 17 13:06:20 orion /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x7b, crflag = 0x1, msg = 0x 5a, frame = 0x5a Jul 17 13:06:27 orion /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x23, crflag = 0x1, msg = 0x 4d, frame = 0x4d 0x8 0x2 0x81 0x90 Jul 17 13:08:25 orion /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x23, crflag = 0x1, msg = 0x 5a, frame = 0x5a Jul 17 13:08:29 orion /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 57 Jul 17 13:09:46 orion /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 106 Jul 17 13:10:31 orion /kernel: i4b-L3-T305_timeout: DISC not answered, cr = 57 Jul 17 13:10:35 orion /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x39, crflag = 0x1, msg = 0x 4d, frame = 0x4d Jul 17 13:13:37 orion /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x39, crflag = 0x1, msg = 0x 5a, frame = 0x5a Jul 17 13:13:41 orion /kernel: i4b-L3-T308_timeout: REL not answered, cr = 106 ... no in- or outgoing connections are accepted any longer 'till I reboot the system. The system (old 486@66MHz) has 2 Fritz! cards ... (from dmesg): isic0 at 0x300 irq 5 flags 0x4 on isa isic0: AVM A1 or AVM Fritz!Card isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x16e0) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x6e0, AddrB=0xee0) isic1 at 0x340 irq 12 flags 0x4 on isa isic1: AVM A1 or AVM Fritz!Card isic1: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x1720) isic1: HSCX 82525 or 21525 Version 2.1 (AddrA=0x720, AddrB=0xf20) ..... i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached ..... Both cards are connected to a TK-switch (Agfeo AS40) on two separate ISDN buses. I do connect to 3 different hosts, using the hdlc protocol (no PPP). The other hosts also run FreeBSD 3.2-stable and 2.8-release and i4b 00.7.00 and do not have these problems. I think, next thing I should do, is upgrading to 00.82.00. BTW: I haven't done this yet, because I do not oversee the consequences: I also track the 3.X-STABLE branch with cvsup - so what happens when I "over install" 00.82.00 and than later cvsup the sys-distribution ? Thanks in advance, Christoph 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?37909718.D4EF80D7>