Date: Wed, 17 Jan 2001 11:01:12 -0500 From: "Howie Xu" <hxu@rios.sitaranetworks.com> To: "Mike Smith" <msmith@freebsd.org> Cc: <freebsd-hackers@freebsd.org> Subject: RE: ISR not triggered upon the interrupts and OS hangs Message-ID: <KEEELJBACBIAGFBCPJMFGEAJCFAA.hxu@rios.sitaranetworks.com> In-Reply-To: <200101170719.f0H7JXl05133@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I am using FreeBSD 3.2, and all the sample drivers in /usr/src/sys/pci/*.c uses pci_map_int(). How can I debug it in 3.2 to know what the OS thinks when the interrupts come in and OS hangs? Thanks again, -Howie > -----Original Message----- > From: Mike Smith [mailto:msmith@freebsd.org] > Sent: Wednesday, January 17, 2001 2:20 AM > To: Howie Xu > Cc: freebsd-hackers@freebsd.org > Subject: Re: ISR not triggered upon the interrupts and OS hangs > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?KEEELJBACBIAGFBCPJMFGEAJCFAA.hxu>