From owner-freebsd-isdn Sun Jul 19 03:32:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00137 for freebsd-isdn-outgoing; Sun, 19 Jul 1998 03:32:28 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29998 for ; Sun, 19 Jul 1998 03:32:17 -0700 (PDT) (envelope-from ernie!bert.kts.org!hm@ppp.net) Received: from casparc.ppp.net (casparc2.ppp.net [194.64.12.42]) by mail.ppp.net (8.8.8/8.8.8) with SMTP id MAA01941; Sun, 19 Jul 1998 12:32:01 +0200 Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0yxqlA-002ZjZC; Sun, 19 Jul 98 12:32 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Sun, 19 Jul 1998 12:11:01 +0200 (CEST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1998-Feb-14) Received: by bert.kts.org via sendmail with stdio id for freebsd-isdn@FreeBSD.ORG; Sun, 19 Jul 1998 12:05:19 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #1 built 1998-Jun-6) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: sometimes ipr0 doesn't send packets - it seems In-Reply-To: <199807180540.HAA02134@rumolt.teuto.de> from Martin Husemann at "Jul 18, 98 07:40:41 am" To: martin@rumolt.teuto.de (Martin Husemann) Date: Sun, 19 Jul 1998 12:05:19 +0200 (CEST) Cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-isdn@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Husemann wrote: > > The usual infamous 'jhs-beep' could be heard, vty6 was showing > > rwth: incoming alert, rwth: call active (ctl 0 , ch 0) etc. > > but no packets. Nothing. Not even a ping to the peer point > > possible. > > Just FYI: I've seen this same thing happen randomly (not very often) with an > old bisnd installation. When it happens, the b-channel interrupt handler is > called with the card denying any need for a b-channel interrupt, so the > handler does nothing and returns. (I've watched the interrupt handler with > remote gdb.) I've put a check into the interrupt handler to print out a message when this happens. Anyway i've no idea currently how to avoid this situation (i'm not even able to reproduce it). hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe A duck is like a bicycle because they both have two wheels except the duck (terry@cs.weber.edu) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message