From owner-freebsd-hackers Tue Jan 16 21: 5:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rios.sitaranetworks.com (rios.sitaranetworks.com [199.103.141.78]) by hub.freebsd.org (Postfix) with ESMTP id AD45537B400 for ; Tue, 16 Jan 2001 21:04:58 -0800 (PST) Received: from mciworlduitoce (gw1.sitaranetworks.com [199.103.141.1]) by rios.sitaranetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CTGYA8C2; Wed, 17 Jan 2001 00:09:08 -0500 From: "Howie Xu" To: Subject: ISR not triggered upon the interrupts and OS hangs Date: Wed, 17 Jan 2001 00:30:27 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 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. The reason I am sure that my handler was never triggered is because the only statement in the ISR is panic("..."). But my machine never panic when the intr comes in (verified by the pci logic analyzer). I did verified the return value of pci_map_int() is right. Btw, I think the OS hangs because it is busy handling the incoming continuous interrupts. Is my judgment making sense? Could anyone give me any hint that might lead to this ISR not being triggered upon interrupt question? Any kind of comments/hints/help would be greatly appreciated. Or if you can let me know a way to debug it in the OS level is also very very welcome. Thanks, -Howie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message