From: Florian Krammel <florian_kr@gmx.de>
To: Kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: [<02282da7>] (usb_hcd_irq+0x0/0x4b) Disabling IRQ #5 - USB Devices do not work
Date: Tue, 07 Dec 2004 21:52:09 +0100 [thread overview]
Message-ID: <1102452729.7531.29.camel@orange-bud> (raw)
In-Reply-To: <1102450409.7531.10.camel@orange-bud>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
> > What chipset is the motherboard ?
I don't know, I don't have the motherboard manuals.
How can I get this information via software?
> > Windows XP and Linux may well hit the same problems with USB.
really? ;)
> > 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"
this is great, thank you! I get the error message but everything works
> > 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 ?
I don't tested this because "irqpoll" solve my problem. Are you
interested in the result? I can try it.
thank you for help...
mfg
florian
--
Florian Krammel <florian_kr@gmx.de>
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-07 21:01 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
[not found] ` <1102450409.7531.10.camel@orange-bud>
2004-12-07 20:52 ` Florian Krammel [this message]
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=1102452729.7531.29.camel@orange-bud \
--to=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