From owner-freebsd-hackers Tue Jan 16 23: 5:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 433B837B698 for ; Tue, 16 Jan 2001 23:05:14 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0H7JXl05133; Tue, 16 Jan 2001 23:19:34 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101170719.f0H7JXl05133@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Howie Xu" Cc: freebsd-hackers@freebsd.org Subject: Re: ISR not triggered upon the interrupts and OS hangs In-reply-to: Your message of "Wed, 17 Jan 2001 00:30:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 23:19:33 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dear Freebsd Hackers, > > Here is a question regarding my bsd device drivers: > > I used the pci_map_int() to register an interrupt handler for my PCI device > (intline = 12). But when the interrupt comes in, the handler (ISR) is not > triggered at all. But the OS hangs and I can see continuous interrupts > coming in on the PCI sniffer. You don't use pci_map_int() on any modern version of FreeBSD; you use bus_alloc_resource() and bus_setup_intr(). Since you don't mention which FreeBSD version you're using, it's hard to be of any more assistance. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message