From owner-freebsd-isdn Mon Jun 7 7:44:53 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from ixori.demon.nl (ixori.demon.nl [195.11.248.5]) by hub.freebsd.org (Postfix) with ESMTP id C0DA415582 for ; Mon, 7 Jun 1999 07:44:25 -0700 (PDT) (envelope-from bart@ixori.demon.nl) Received: from localhost.ixori.demon.nl (localhost.ixori.demon.nl [127.0.0.1]) by ixori.demon.nl (8.9.3/8.9.1) with ESMTP id QAA44090; Mon, 7 Jun 1999 16:48:30 +0200 (CEST) (envelope-from bart@ixori.demon.nl) Date: Mon, 7 Jun 1999 16:48:30 +0200 (CEST) From: Bart van Leeuwen To: Martin Husemann Cc: "Frank J. Beckmann" , freebsd-isdn@freebsd.org Subject: RE: ELSA MicroLink ISDN/PCF In-Reply-To: <000001beb0a7$dd556220$53cb08d4@martins.teuto.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 7 Jun 1999, Martin Husemann wrote: > > and what are the 2 LEDs for? > > They are not used by I4B (you can toggle them on/off by software, but > Hellmuth didn't find a good reason to do so). > > > I get a lot messages: > > > > i4b-L1-isicintr: WARNING: unit 0, No IRQ from HSCX/ISAC! > > This message is harmless. It means the interrupt handler was called but > found nothing to do. There are a few (more or less) legitimate reasons why > this will happen, and I think this WARNING: has to be removed from I4B. > Think of two PCI cards sharing the same interrupt... > I can fully confirm that... have had a working system that gives that message for a long time now (and indeed I usually simply patch i4b a little bit to stop it from spamming my log and console with it..) Disabling the message, or maybe better, only give it when debug info is requested would be highly apreciated. Bart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message