From owner-freebsd-hackers Sat Jul 4 11:59:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27526 for freebsd-hackers-outgoing; Sat, 4 Jul 1998 11:59:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27510 for ; Sat, 4 Jul 1998 11:59:14 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id MAA18298; Sat, 4 Jul 1998 12:54:20 -0600 (MDT) Date: Sat, 4 Jul 1998 12:54:20 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807041854.MAA18298@narnia.plutotech.com> To: "Larry S. Lile" cc: hackers@FreeBSD.ORG Subject: Re: Problems with irq 9(2)? Newsgroups: pluto.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. Shouldn't you clear the interrupt status (via the reset), before processing the event in your interrupt handler instead of the other way around? I would expect you to potentially miss interrupts the other way around, but I don't know anything about the specifics of the hardware you're working with. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message