linux-kernel - Re: un/shared IRQ problem (was: Re: 2.6.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061018232603.585d14c3.akpm@osdl.org>
Date:	Wed, 18 Oct 2006 23:26:03 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Martin Lorenz <martin@...enz.eu.org>
Cc:	Jesse Brandeburg <jesse.brandeburg@...il.com>,
	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: un/shared IRQ problem (was: Re: 2.6.18 - another DWARF2)

On Wed, 18 Oct 2006 08:34:31 +0200
Martin Lorenz <martin@...enz.eu.org> wrote:

> On Tue, Oct 17, 2006 at 11:52:16AM -0700, Jesse Brandeburg wrote:
> > On 10/16/06, Martin Lorenz <martin@...enz.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

Could we see the /proc/interrupts please, so we can find out where the
clash is happening?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/