From owner-freebsd-isdn Thu Apr 2 15:41:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01893 for freebsd-isdn-outgoing; Thu, 2 Apr 1998 15:41: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 PAA01874 for ; Thu, 2 Apr 1998 15:41:42 -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 BAA21573; Fri, 3 Apr 1998 01:41:42 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199804022341.BAA21573@rvc1.informatik.ba-stuttgart.de> Subject: Re: i4b-L1-F_ill:What is this? (fwd) In-Reply-To: from Blaz Zupan at "Apr 2, 98 06:33:50 pm" To: blaz@gold.amis.net (Blaz Zupan) Date: Fri, 3 Apr 1998 01:41:41 +0200 (MET DST) Cc: hm@hcs.de, freebsd-isdn@FreeBSD.ORG 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 > > I just had a hard time debugging a non-running isdn4bsd setup where the > > card was at IRQ 12. IRQ 12 seems to be hardwired somehow on newer hard- > > ware to the PS/2 Bus Mouse port, and after moving the card to a different > > IRQ (IRQ 5 in this case) all worked as expected. > > Unfortunatelly bisdn worked just fine without any problems in this machine This reminds me of the SMP problem -- bisdn worked but i4b didn't. There is a workaround for this that might help even if you don't have a multiprocessor board. So please add options "I4B_SMP_WORKAROUND" to your kernel configuration file and tell us what happened. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message