From owner-freebsd-hackers Sun Jan 21 9:57:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from VL-MS-MR001.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 7CF2437B401 for ; Sun, 21 Jan 2001 09:57:36 -0800 (PST) Received: from jehovah ([24.201.144.31]) by VL-MS-MR001.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7IXVF01.WSJ; Sun, 21 Jan 2001 12:57:15 -0500 Message-ID: <009201c083d3$d0054bc0$1f90c918@jehovah> From: "Bosko Milekic" To: "Alex" , References: Subject: Re: Problems attaching an interrupt handler Date: Sun, 21 Jan 2001 12:58:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This: bus_teardown_intr(dev, sc->irq, sc->ih) != 0 ); looks pretty odd. See your ir_detach(). Alex wrote: > Hi, > > I started experimenting with kernel hacking to write an > infrared device driver. Therfore I read Alexander Langer's > article on DaemonNews and started modifying the led.c > example code. > > Unfortunately I can't get my interrupt handler working. > > Could anyone please have a short look on my code. > > On loading the module the first time everything stays > stable and vmstat -i shows 1 INT on my device. After > unloading the module and reloading it the kernel > crashes on the next incoming interrupt. > > Any ideas? > > Alex > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message