Messages in this thread | | | Date | Wed, 18 Oct 2006 08:34:31 +0200 | From | Martin Lorenz <> | Subject | un/shared IRQ problem (was: Re: 2.6.18 - another DWARF2) |
| |
On Tue, Oct 17, 2006 at 11:52:16AM -0700, Jesse Brandeburg wrote: > On 10/16/06, Martin Lorenz <martin@lorenz.eu.org> wrote: > >just got the following on resume: > > > >[87026.706000] [<c0251745>] 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
gruss mlo -- Dipl.-Ing. Martin Lorenz
They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. Benjamin Franklin
please encrypt your mail to me GnuPG key-ID: F1AAD37D get it here: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D
ICQ UIN: 33588107 - 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/
| |