From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 - another DWARF2
Date: Tue, 17 Oct 2006 11:52:16 -0700 [thread overview]
Message-ID: <4807377b0610171152tfea31c1v3f907dcaf0a58509@mail.gmail.com> (raw)
In-Reply-To: <20061017063710.GA27139@gimli>
On 10/16/06, Martin Lorenz <martin@lorenz.eu.org> wrote:
> just got the following on resume:
>
> [87026.242000] usb 4-2: USB disconnect, address 18
> [87026.448000] usb 4-2: new full speed USB device using uhci_hcd and address
> 20
> [87026.613000] usb 4-2: configuration #1 chosen from 1 choice
> [87026.704000] IRQ handler type mismatch for IRQ 90
> [87026.704000] [<c0103d7c>] show_trace_log_lvl+0x5b/0x16d
> [87026.704000] [<c01044cb>] show_trace+0xf/0x11
> [87026.705000] [<c01045ce>] dump_stack+0x15/0x17
> [87026.705000] [<c01403d7>] setup_irq+0x17d/0x190
> [87026.705000] [<c0140466>] request_irq+0x7c/0x98
> [87026.706000] [<c0251745>] e1000_open+0xcd/0x1a4
> [87026.707000] [<c029565c>] dev_open+0x2b/0x62
> [87026.708000] [<c0294181>] dev_change_flags+0x47/0xe4
> [87026.709000] [<c02c7cd1>] devinet_ioctl+0x252/0x556
> [87026.711000] [<c028b5a3>] sock_ioctl+0x19a/0x1be
> [87026.712000] [<c016b6af>] do_ioctl+0x1f/0x62
> [87026.712000] [<c016b937>] vfs_ioctl+0x245/0x257
> [87026.713000] [<c016b995>] sys_ioctl+0x4c/0x67
> [87026.714000] [<c0102db3>] syscall_call+0x7/0xb
> [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.
from your dmesg
[ 0.289935] Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
[ 0.290030] Copyright (c) 1999-2006 Intel Corporation.
[ 0.290196] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level,
low) -> IRQ 201
[ 0.291176] PCI: Setting latency timer of device 0000:02:00.0 to 64
[ 0.336827] e1000: 0000:02:00.0: e1000_probe: (PCI
Express:2.5Gb/s:Width x1) 00:16:d3:22:9b:82
[ 0.381316] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
[ 0.381553] netconsole: not configured, aborting
[ 0.381759] libata version 2.00 loaded.
[ 0.381815] ahci 0000:00:1f.2: version 2.0
[ 0.381835] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level,
low) -> IRQ 201
and
[ 7.107822] USB Universal Host Controller Interface driver v3.0
[ 7.107988] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level,
low) -> IRQ 201
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.
Jesse
next prev parent reply other threads:[~2006-10-17 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 6:37 Martin Lorenz
2006-10-17 18:52 ` Jesse Brandeburg [this message]
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
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=4807377b0610171152tfea31c1v3f907dcaf0a58509@mail.gmail.com \
--to=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
all inboxes | Powered by JetHome®