From owner-freebsd-questions Tue Jan 16 20:36:16 2001 Delivered-To: freebsd-questions@freebsd.org Received: from rios.sitaranetworks.com (rios.sitaranetworks.com [199.103.141.78]) by hub.freebsd.org (Postfix) with ESMTP id 5E76D37B401 for ; Tue, 16 Jan 2001 20:35:57 -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 CTGYA8BS; Tue, 16 Jan 2001 23:40:07 -0500 From: "Howie Xu" To: Subject: ISR not being called upon the interrupt comes in Date: Wed, 17 Jan 2001 00:01:26 -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-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I used pci_map_int() to register an interrupt handler for my device (intline = 12). But when the interrupt comes in, the handler (ISR) did not kick in at all. The reason I am sure that my handler was never called 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). Could anyone give me any hint that might lead to this ISR not being called upon interrupt? I did verified the return value of pci_map_int() is right. Actually, I looked deep in the pci_map_int() implementation, and it simply calls intr_create() and intr_connect() in the sys/kern/kern_intr.c. Any kind of comments/hints/help would be greatly appreciated. Or if you can let me know a way to debug it is also very very welcome. Thanks, -Howie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message