From owner-freebsd-isdn Sun May 31 10:02:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14155 for freebsd-isdn-outgoing; Sun, 31 May 1998 10:02:52 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.dinoex.sub.org (root@mail.dinoex.sub.de [195.243.29.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14128 for ; Sun, 31 May 1998 10:02:12 -0700 (PDT) (envelope-from dirk.meyer@dinoex.sub.org) Received: (from uucp@localhost) by mail.dinoex.sub.org (8.8.7/8.8.7) with UUCP id TAA17556 for freebsd-isdn@FreeBSD.ORG; Sun, 31 May 1998 19:02:06 +0200 (CEST) Received: from gate.dinoex.sub.org (dinoex@localhost) by net2.dinoex.sub.org (8.8.7/8.8.7) with BSMTP id TAA09676 for ; Sun, 31 May 1998 19:00:31 +0200 (CEST) To: freebsd-isdn@FreeBSD.ORG Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: still problems with i4b 0.51 (+rework Layer1) Date: Sun, 31 May 1998 19:00:05 +0200 X-Mailer: Dinoex 1.68 References: X-Gateway: ZCONNECT gate.dinoex.sub.org [UNIX/Connect v0.76-m5] X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-ZC-VIA: 19980531000000S+2@dinoex.sub.org Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Malte Lance wrote:, > > here my status on i4b-0.51 with layer1-rework patch form this list. > > i4b is at version 0.61 > How about an upgrade ? sure already done, but the same problem occurs under 0.60, 0.61 has not been tested yet. > > kernel crash with panic "receving 3" > > just after connect. i can't trace it down, but it runs with BISDN fine. I think i could be a "AOC Message" on the line. every crash costs me about 40 mins file system check, so please don't mind that i test this not immediatly. I can't locate the origing of this in the kernel. Any hints welcome, how i can avoid the crash. regards Dirk -- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany -- Tel. +49-5606-6512 . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message