From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: florian <florian_kr@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [<02282da7>] (usb_hcd_irq+0x0/0x4b) Disabling IRQ #5 - USB Devices do not work
Date: Mon, 06 Dec 2004 13:28:20 +0000 [thread overview]
Message-ID: <1102339694.13485.26.camel@localhost.localdomain> (raw)
In-Reply-To: <1102333735.5095.4.camel@orange-bud>
On Llu, 2004-12-06 at 11:48, florian wrote:
> How can I enable "USB Legacy Support" without errors?
> How can I resolve the problem with the USB devices?
What chipset is the motherboard ?
> I've found via google some BIOS Bugs for "USB Legacy Support", but this
> bug occurs only on Windows XP (I don't found this for Linux). I tried
> allready to update my BIOS and now USB is disabled for all devices
> (Mouse, Printer, Scanner, USB-FlashMemory)
Windows XP and Linux may well hit the same problems with USB.
> irq 5: nobody cared! (screaming interrupt?)
> irq 5: Please try booting with acpi=off and report a bug
> Stack pointer is garbage, not printing trace
> handlers:
> [<02282da7>] (usb_hcd_irq+0x0/0x4b)
> Disabling IRQ #5
The latest FC3 kernel should have new enough -ac patches to run on boxes
with
totally broken BIOS IRQ routing. Try the boot option "irqpoll"
> ehci_hcd 0000:00:13.2: EHCI Host Controller
> ehci_hcd 0000:00:13.2: BIOS handoff failed (160, 1010001)
> ehci_hcd 0000:00:13.2: continuing after BIOS bug...
> irq 5: nobody cared! (screaming interrupt?)
> irq 5: Please try booting with acpi=off and report a bug
> Stack pointer is garbage, not printing trace
This is all interesting seen as one. It implies the BIOS handover failed
and
then we get an IRQ mess.
> ehci_hcd 0000:00:13.2: EHCI Host Controller
> ehci_hcd 0000:00:13.2: BIOS handoff failed (160, 1010001)
> ehci_hcd 0000:00:13.2: continuing after BIOS bug...
> irq 5: nobody cared! (screaming interrupt?)
> irq 5: Please try booting with acpi=off and report a bug
> Stack pointer is garbage, not printing trace
Ditto, and this is quite possibly the root cause. That suggests the BIOS
handover code for EHCI is insufficient for some cases (and it appears to
be looking at the code quickly - it should register IRQ 5 before doing a
handover which it does but it probably needs to just ack and mask IRQ 5
during the handover. It could be another device breaking IRQ5 however)
What occurs if you build a kernel with EHCI disabled, ditto what occurs
if you boot with init=/bin/sh and then load ohci before ehci ?
next prev parent reply other threads:[~2004-12-06 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 11:48 [<02282da7>] (usb_hcd_irq+0x0/0x4b) Disabling IRQ #5 - USB Devices do not work florian
2004-12-06 13:28 ` Alan Cox [this message]
[not found] ` <1102450409.7531.10.camel@orange-bud>
2004-12-07 20:52 ` Florian Krammel
2004-12-08 9:15 ` Florian Krammel
2004-12-08 11:03 ` Alan Cox
2004-12-12 13:38 ` Florian Krammel
2004-12-06 13:29 ` Florian Krammel
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=1102339694.13485.26.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=florian_kr@gmx.de \
--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