Date: Sat, 9 Oct 1999 19:40:42 +0200 (CEST) From: hm@kts.org (Hellmuth Michaelis) To: mranner@netway.at Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: cause 63 - problem with Fritz! PCI and i4b-0.83 Message-ID: <m11a0U6-00002XC@bert.kts.org> In-Reply-To: <XFMail.991009152320.mranner@netway.at> from Michael Ranner at "Oct 9, 1999 3:23:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Ranner wrote: > Nearly every day (20h - 30h uptime) I have the following > problem with i4b-0.83 under FreeBSD 3.2-RELEASE: [...] > Oct 6 11:10:22 files /kernel: i4b-L1-timer4_expired: state = F3 Deactivated > Oct 6 11:10:22 files /kernel: i4b-L2-i4b_mph_status_ind: unit 0, persistent > deactivation! > Oct 6 11:10:22 files /kernel: i4b-L3-i4b_mdl_status_ind: STI_PDEACT: unit 0 > TEI = 0 = 0x00 [...] > I have to reboot the system to fix this problem Recently i bought another PBX (i needed one with a clean internal protocol stack and which switches off Layer 1, which my other one didn't) to be able to debug the i4b-L1-timer4_expired messages reported by others. Since i moved my ISDN i4b-operated equipment to this PBX (which now shuts Layer 1 properly down when noone is using the bus) i've seen the above described effect once. It was a 3.2-STABLE system with a Teles 16.3 and i also had to reboot to recover from this. This seems to be a bug in i4b. I doubt i'll currently get the time and silence necessary to debug this. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... 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?m11a0U6-00002XC>