From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762848AbXK3J3c (ORCPT ); Fri, 30 Nov 2007 04:29:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756896AbXK3J3B (ORCPT ); Fri, 30 Nov 2007 04:29:01 -0500 Received: from nf-out-0910.google.com ([64.233.182.186]:35273 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755322AbXK3J26 (ORCPT ); Fri, 30 Nov 2007 04:28:58 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WLIDB2zVPIlQRbxQiVl/Qc1DTiOW+6+9Ba2zS9mVOQzFPxcu41vzu435h59MGrfa3QlOZWIJRQWvjncuEbo7gUiNOv2xptQCEds+ANS+IS2TIG4lcgxELo5C72xzWaaYbJ79DNSFYHHsTPDnJNJhWxxBgeDBknngDnSTvnWjQqw= Message-ID: <40dfeece0711300128s731b3227xaa0b5982193e4b12@mail.gmail.com> Date: Fri, 30 Nov 2007 09:28:56 +0000 From: "Chris Rutherford" To: linux-kernel@vger.kernel.org Subject: ldd irq problem In-Reply-To: <40dfeece0711291447m2efa4f40i5c2c22a4273ecbc0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40dfeece0711291447m2efa4f40i5c2c22a4273ecbc0@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Helo lkml, I'm trying to write a LDD but I have got a bug. Any ideas what i might be doing wrong? ret = request_irq(12, handler, SA_INTERRUPT | SA_SHIRQ, "sha1 handler", DEVICE_NAME); printk (KERN_INFO "req irq %d \n", ret); enable_irq(12); I am working on a linux device driver and trying to handle interupts. using the code above I get the log messages below. req irq 0 Unbalanced enable for IRQ 12 BUG: warning at kernel/irq/manage.c:118/enable_irq() [] enable_irq+0x54/0x87 [] __driver_attach+0x0/0x5d [] device_probe+0x16b/0x173 [raggedstone1] [] pci_device_probe+0x36/0x57 [] driver_probe_device+0x42/0x91 [] __driver_attach+0x38/0x5d [] bus_for_each_dev+0x37/0x59 [] driver_attach+0x11/0x13 [] __driver_attach+0x0/0x5d [] bus_add_driver+0x6b/0xfd [] __pci_register_driver+0x47/0x63 [] sys_init_module+0x1732/0x18b5 [] do_sync_read+0xb6/0xf1 [] dput+0x2a/0x119 [] sysenter_past_esp+0x56/0x79 Has any one seen this type of bug message before? any idea what could be causing it. Thanks Chris