Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945979AbWJSHB3 (ORCPT ); Thu, 19 Oct 2006 03:01:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161338AbWJSHB3 (ORCPT ); Thu, 19 Oct 2006 03:01:29 -0400 Received: from smtp.osdl.org ([65.172.181.4]:38530 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1161328AbWJSHB2 (ORCPT ); Thu, 19 Oct 2006 03:01:28 -0400 Date: Thu, 19 Oct 2006 00:01:09 -0700 From: Andrew Morton To: Martin Lorenz Cc: Jesse Brandeburg , linux-kernel@vger.kernel.org, "Eric W. Biederman" Subject: Re: un/shared IRQ problem (was: Re: 2.6.18 - another DWARF2) Message-Id: <20061019000109.626170f7.akpm@osdl.org> In-Reply-To: <20061019063921.GJ6189@gimli> References: <20061017063710.GA27139@gimli> <4807377b0610171152tfea31c1v3f907dcaf0a58509@mail.gmail.com> <20061018063431.GE20238@gimli> <20061018232603.585d14c3.akpm@osdl.org> <20061019063921.GJ6189@gimli> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2977 Lines: 79 On Thu, 19 Oct 2006 08:39:21 +0200 Martin Lorenz wrote: > On Wed, Oct 18, 2006 at 11:26:03PM -0700, Andrew Morton wrote: > > On Wed, 18 Oct 2006 08:34:31 +0200 > > Martin Lorenz wrote: > > > > > On Tue, Oct 17, 2006 at 11:52:16AM -0700, Jesse Brandeburg wrote: > > > > On 10/16/06, Martin Lorenz wrote: > > > > >just got the following on resume: > > > > > > > > > >[87026.706000] [] e1000_open+0xcd/0x1a4 > > > > >[87026.714000] DWARF2 unwinder stuck at syscall_call+0x7/0xb > > > > >[87026.715000] Leftover inexact backtrace: > > > > >[87026.715000] e1000: eth0: e1000_request_irq: Unable to allocate interrupt > > > > >Error: -16 > > > > > > > > I'm pretty sure this isn't an e1000 problem. you need to talk to > > > > whoever is maintaining the IRQ subsystem for x86. E1000 is attempting > > > > to register a shared interrupt and someone has already registered that > > > > interrupt unshared. > > > > > > interestingly though it always involves e1000 when I see dumps like this. > > > I already reported more of those :-) > > > this one dosen't seem to do any harm to system stability. it occurs on every > > > suspend/resume and I can circumvent it by disabling msi > > > > > > > > > > > looks like several devices are sharing IRQ 201 (aka GSI 16) and ahci > > > > or usb uhci_hcd is likely the problem, or the (acpi) power management > > > > subsystem. > > > > > > > > Hope this helps get the right people involved. > > > > > > thank you > > > > Could we see the /proc/interrupts please, so we can find out where the > > clash is happening? > > > here you are > > ~# cat /proc/interrupts > CPU0 CPU1 > 0: 76521957 2009390 IO-APIC-edge timer > 1: 39599 0 IO-APIC-edge i8042 > 8: 128 0 IO-APIC-edge rtc > 9: 415044 0 IO-APIC-level acpi > 12: 862451 0 IO-APIC-edge i8042 > 58: 68014 326850 PCI-MSI libata > 66: 508910 17187 IO-APIC-level sdhci:slot0, uhci_hcd:usb3 > 74: 3156375 0 IO-APIC-level uhci_hcd:usb2, ohci1394, HDA Intel > 82: 134828 0 IO-APIC-level uhci_hcd:usb4, ehci_hcd:usb5 > 90: 46548 0 PCI-MSI eth0 > 201: 100133 0 IO-APIC-level uhci_hcd:usb1, yenta, i915@pci:0000:00:02.0 > NMI: 0 0 > LOC: 78530935 78520308 > ERR: 0 > MIS: 0 > There are already three interrupt sources on 201, so they are all happy to share. It's e1000. Jesse, you fibbed ;) static int e1000_request_irq(struct e1000_adapter *adapter) { ... if (adapter->have_msi) flags &= ~IRQF_SHARED; - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/