From owner-freebsd-isdn Thu Apr 2 01:58:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14481 for freebsd-isdn-outgoing; Thu, 2 Apr 1998 01:58:43 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA14466 for ; Thu, 2 Apr 1998 01:58:41 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2680 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Thu, 2 Apr 1998 11:58:29 +0200 (METDST) (Smail-3.2.0.97 1997-Aug-19 #16 built 1997-Oct-22) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0yKgmz-0000ayC; Thu, 2 Apr 98 12:00 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: i4b-L1-F_ill:What is this? In-Reply-To: <199804011921.VAA05846@peedub.muc.de> from Gary Jennejohn at "Apr 1, 98 09:21:54 pm" To: freebsd-isdn@FreeBSD.ORG (ISDN Mailinglist) Date: Thu, 2 Apr 1998 12:00:05 +0200 (METDST) Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (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 >From the keyboard of Gary Jennejohn: > >> >> xxx_ISAC_IRQ..: RME: Input Buffer Overflow... > >> > >> I see exactly the same thing with a Teles 16.3 card when I boot and _before_ > >> isdnd starts. Once the daemon is running the messages disappear. > > > >Hmm - Gary, i remember we found out that you have got a constant-active > >("daueraktiv" in german, don't know the english word) S0 bus, perhaps > >this is the cause ?! > > I have the same suspicion. Have to run isdntrace to confirm that the > message is the result of a "keep alive" from the NT. Eric just sent in a trace, and it seems that either as soon as his exchange detects state changes in L1 or perhaps constantly sends TEI check request messages with a group TEI, which causes all devices with an assigned TEI to answer. This TEI check request message is then sent every second. These TEI check request messages seem to be the cause of the RME ... messages, because the i4b stack is not ready to handle those messages at boot time yet. As soon as i4b requests a TEI (when the first connection is made), one is granted and from then on the TEI check request messages are properly answered. The only questions arising from this are: - should the ISAC irqs be enabled later when the whole machine is up, and how can the state "the machine is up and ready to serve irq's" be detected by a driver for all *BSD's ? - although Q.921 doesn't require this, shall a TEI request procedure be initiated on arrival of a TEI check request with a group TEI and no local TEI assigned yet ? Comments ? hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm@hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message