From owner-freebsd-isdn  Sat Feb 28 07:11:53 1998
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA16249
          for freebsd-isdn-outgoing; Sat, 28 Feb 1998 07:11:53 -0800 (PST)
          (envelope-from owner-freebsd-isdn@FreeBSD.ORG)
Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16233
          for <freebsd-isdn@FreeBSD.ORG>; Sat, 28 Feb 1998 07:11:29 -0800 (PST)
          (envelope-from helbig@Informatik.BA-Stuttgart.DE)
Received: (from helbig@localhost)
	by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id QAA00257
	for freebsd-isdn@FreeBSD.ORG; Sat, 28 Feb 1998 16:11:26 +0100 (MET)
From: Wolfgang Helbig <helbig@Informatik.BA-Stuttgart.DE>
Message-Id: <199802281511.QAA00257@rvc1.informatik.ba-stuttgart.de>
Subject: Re: AVM A1 Setup bug on NetBSD?
In-Reply-To: <199802281234.NAA01463@rumolt.teuto.de> from Martin Husemann at "Feb 28, 98 01:34:29 pm"
To: freebsd-isdn@FreeBSD.ORG
Date: Sat, 28 Feb 1998 16:11:25 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL30 (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

> > do you mean messages like that?
> > I have an NetBSD 1.3 with an _CREATIX_ card. 
> > 
> > Feb 27 00:00:07 hal /netbsd: i4b-L2-i4b_tei_assign: tx TEI ID_Request
> > Feb 27 00:00:08 hal /netbsd: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3
> > Feb 27 00:00:08 hal /netbsd: i4b-L2-i4b_tei_assign: tx TEI ID_Request
> > Feb 27 00:00:09 hal /netbsd: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3
> > Feb 27 00:00:09 hal /netbsd: i4b-L2-i4b_tei_assign: tx TEI ID_Request
> > Feb 27 00:00:10 hal /netbsd: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3
> 
> Yes - this is very much likeley due to the interrupt handler not 
> being called.

The same happened on a FreeBSD SMP system. The workaround was
to MASK/UNMASK the ISAC/HSCX interrupts every time an ISAC command
is issued (see layer1/i4b_isac.c)

BTW, on my ancient motherboard (UM8810P-AIO / Phoenix BIOS 1994) IRQ 10
is used by ``Non_SMI CPU support''. Don't know, what that means.

Wolfgang

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message