From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Tobias Ringstrom <tori@tellus.mine.nu>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
andrewm@uow.edu.au, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 3c59x: Using bad IRQ 0
Date: Fri, 24 Nov 2000 18:14:20 -0500 [thread overview]
Message-ID: <3A1EF64C.BFE05CE8@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10011211723380.4687-100000@penguin.transmeta.com>
Linus Torvalds wrote:
>
> On Tue, 21 Nov 2000, Jeff Garzik wrote:
> >
> > A caveat to this whole scheme is that usb-uhci -already- calls
> > pci_enable_device before checking dev->irq, and yet cannot get around
> > the "assign IRQ to USB: no" setting in BIOS. I hope that is an
> > exception rather than the rule.
>
> Do we have a recent report of this with full PCI debug output? It might
> just be another unlisted intel irq router..
Actually, I -was- able to reproduce this problem on my SMP PIIX4 box
here. But as of test11-final, I am no longer able to reproduce it.
Maybe some intrepid testers are willing to test 2.4.0-test11 with these
BIOS settings:
PNP OS: Yes
Assign IRQ to USB: No
It works for me... :)
Jeff
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-24 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 19:09 3c59x: Using bad IRQ 0 Tobias Ringstrom
2000-11-21 19:28 ` Jeff Garzik
2000-11-21 22:18 ` Tobias Ringstrom
2000-11-23 17:06 ` Linus Torvalds
2000-11-23 18:21 ` Tobias Ringstrom
2000-11-23 18:32 ` Linus Torvalds
2000-11-24 0:14 ` Jeff Garzik
2000-11-22 1:26 ` Linus Torvalds
2000-11-24 14:59 ` Erik Mouw
2000-11-24 23:14 ` Jeff Garzik [this message]
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=3A1EF64C.BFE05CE8@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tori@tellus.mine.nu \
--cc=torvalds@transmeta.com \
/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