public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Lorenz <martin@lorenz.eu.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: un/shared IRQ problem (was: Re: 2.6.18 - another DWARF2)
Date: Thu, 19 Oct 2006 08:39:21 +0200	[thread overview]
Message-ID: <20061019063921.GJ6189@gimli> (raw)
In-Reply-To: <20061018232603.585d14c3.akpm@osdl.org>

On Wed, Oct 18, 2006 at 11:26:03PM -0700, Andrew Morton wrote:
> On Wed, 18 Oct 2006 08:34:31 +0200
> Martin Lorenz <martin@lorenz.eu.org> wrote:
> 
> > 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
> 
> 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


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

  reply	other threads:[~2006-10-19  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17  6:37 2.6.18 - another DWARF2 Martin Lorenz
2006-10-17 18:52 ` Jesse Brandeburg
2006-10-18  6:34   ` un/shared IRQ problem (was: Re: 2.6.18 - another DWARF2) Martin Lorenz
2006-10-19  6:26     ` Andrew Morton
2006-10-19  6:39       ` Martin Lorenz [this message]
2006-10-19  7:01         ` Andrew Morton
2006-10-19 14:48           ` Eric W. Biederman
2006-10-19 17:14             ` Andrew Morton
2006-10-20  8:37               ` Martin Lorenz
2006-10-20  8:47                 ` Andrew Morton
2006-10-20  9:17                   ` Martin Lorenz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061019063921.GJ6189@gimli \
    --to=martin@lorenz.eu.org \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox