From owner-freebsd-isdn Wed Jun 21 12: 0:15 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 4EC2B37BA16 for ; Wed, 21 Jun 2000 12:00:10 -0700 (PDT) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id VAA02994; Wed, 21 Jun 2000 21:00:38 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.1) id e5LIoNJ00675; Wed, 21 Jun 2000 20:50:23 +0200 (MEST) From: Martin Husemann Message-Id: <200006211850.e5LIoNJ00675@rumolt.teuto.de> Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: from Paul Herman at "Jun 20, 2000 12:57:39 pm" To: pherman@frenchfries.net (Paul Herman) Date: Wed, 21 Jun 2000 20:50:23 +0200 (MEST) Cc: garyj@muc.de (Gary Jennejohn), freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (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 > Not ready for defeat, I persued the clrirq idea, and found a clrirq > function, for elsa ISA cards which solely consisted of the line: > > outb(sc->sc_iobase1 + 0x07, 0x00) We've been told by the ELSA people that this is absolutley necessary on that card - and it works. > Which hapens to be TRIGGER register, at least on the ISA card (?). I > put that in the interrupt function, which called outb() if it looped > more than 5 times. Still the same lock up during boot. :( This is a complete different card, so that won't work for it, of course. > I'm out of ideas. Does anybody have a tech contact at ELSA? No email > addresses on their web site. Maybe I'll ask the i4linux crowd. Yes, me (and some others) have. ELSA has been very helpful and supportive. In fact I'm running the ELSA Quickstep PCI card in one of our main servers (but of course using NetBSD) and randomly see the problem there too, so I actually have motivation to dig into this further. But I don't have time right now (but will have in a few days). Have you ever tried booting with the ISDN connection unpluged and then plugging it in later? This should eliminate the hard problem, but keeps the potential for random lockups. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message