From: Len Brown <len.brown@intel.com>
To: Jurgen Kramer <gtm.kramer@inter.nl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm3 USB ehci IRQ problem
Date: 05 Jul 2004 15:02:47 -0400 [thread overview]
Message-ID: <1089054167.15653.51.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FEF3E@hdsmsx403.hd.intel.com>
On Sun, 2004-06-27 at 08:02, Jurgen Kramer wrote:
> With 2.6.7-mm3 I am missing my USB 2.0 memory stick. It doesn't show
> up in the usb device listing. But when I unplug it I get:
>
> irq 23: nobody cared!
> [<c0108106>] __report_bad_irq+0x2a/0x8b
> [<c01081f0>] note_interrupt+0x6f/0x9f
> [<c0108473>] do_IRQ+0x10c/0x10e
> [<c0106850>] common_interrupt+0x18/0x20
> handlers:
> [<f9d0f65c>] (snd_emu10k1_interrupt+0x0/0x3c4 [snd_emu10k1])
> Disabling IRQ #23
>
> The soundcard is still usable but there are no new interrupts.
>
> When I try to reload the ehci module I get:
>
> ACPI: PCI interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 23
> ehci_hcd 0000:00:1d.7: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI
> Controller
> ehci_hcd 0000:00:1d.7: BIOS handoff failed (104, 1010001)
> ehci_hcd 0000:00:1d.7: can't reset
> ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -95
> ehci_hcd: probe of 0000:00:1d.7 failed with error -95
>
> IRQ23 is normally shared between emu10k1 and the ehci controller
> without problems.
it worked normally in 2.6.7 vanilla?
it would be interesting to know if booting with "acpi_os_name=Linux"
makes any difference.
-Len
next parent reply other threads:[~2004-07-05 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FEF3E@hdsmsx403.hd.intel.com>
2004-07-05 19:02 ` Len Brown [this message]
2004-07-05 20:16 ` 2.6.7-mm3 USB ehci IRQ problem Jurgen Kramer
2004-07-05 20:33 ` Jurgen Kramer
2004-07-05 21:15 ` Len Brown
2004-07-06 16:15 ` Jurgen Kramer
2004-07-06 16:27 ` Len Brown
2004-06-27 12:02 Jurgen Kramer
2004-06-27 18:42 ` Andrew Morton
2004-06-27 20:08 ` Jurgen Kramer
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=1089054167.15653.51.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=gtm.kramer@inter.nl.net \
--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