From owner-freebsd-hackers Fri Jul 3 09:55:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21057 for freebsd-hackers-outgoing; Fri, 3 Jul 1998 09:55:58 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21052 for ; Fri, 3 Jul 1998 09:55:54 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id MAA13085; Fri, 3 Jul 1998 12:52:44 -0400 (EDT) Date: Fri, 3 Jul 1998 12:52:43 -0400 (EDT) From: "Larry S. Lile" To: Mike Smith cc: David Greenman , Mike Smith , hackers@FreeBSD.ORG Subject: Re: Problems with irq 9(2)? In-Reply-To: <199807030448.VAA04008@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Jul 1998, Mike Smith wrote: > > > > > > On Wed, 1 Jul 1998, David Greenman wrote: > > > > > >Anyway, the card has a register (isrp) that has a bit that shows whether > > > >or not the card can interrrupt the 8259 on its irq line. This works for > > > >the first interrupt but as soon as I enter an spl loop that bit goes > > > >high, saying he can't interrupt, and never drops even after exiting the > > > >spl loop. > > > > > > Sounds to me like you aren't acking the interrupt in your ISR. > > > > Could I get you to take a peek at whats going on? The adapter spec is > > at (or at least the pages on the status registers) > > http://ppdbooks.pok.ibm.com:80/cgi-bin/bookmgr/bookmgr.cmd/BOOKS/BK8R1001 > > /1.4.9.4 > > and the code for the driver is at http://anarchy.stdio.com (or you can get > > to it at http://www.jurai.net/~winter/tr/tr.html). I have been working > > from the MACH source and I can't see what i'm doing wrong. > > > > Whats got me really confused is bit 1 in the ISRP high (even) which > > is called User interrupt blocked? And worst is I can't seem to > > reset it. > > When you say this, have you tried writing a 0 to it? Yeah, I tried reset and rw the bit in the register. The mach driver uses reset. > Also, how about this snippet: > > ADAPTER INTERRUPT ENABLE > For PC System with PC I/O Bus: An I/O Write (OUT instruction) to X'0A23' (adapter 0) or X'0A27' (adapter 1) resets > and re-enables the adapter interrupt generation circuitry. An I/O read to this address is reserved. Seems like swatting flies with a 2x4. I dug into the IBM sample driver for aix and that is what their doing. I guess its good enough. > Apart from that, I would be asking IBM for help... I finally got through to 3rd line support at IBM. I should get to talk to a developer sometime next week (I hope). I started hitting the interrupt reset pio just before I leave my interrupt handler and things seem to be better. Now it just loops like mad when it gets a packet, on to new problems. Thanks for the help. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message