From: Pete Toscano <pete@research.netsol.com>
To: linux-kernel@vger.kernel.org
Subject: please help: usb and irq problem with 2.2.18 and 2.4.0-test?
Date: Fri, 22 Dec 2000 17:12:50 -0500 [thread overview]
Message-ID: <20001222171250.A28612@tesla.admin.cto.netsol.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
i've asked a few times, both off-list and on and nobody seems to be able
to help.
quite a few people are seeing usb fail (with the "device not accepting
new address" error messages) on the 2.2.18 and 2.4.0-testX kernels with
smp enabled when using a mobo with the apollo pro 133a chipset. when
apic is disabled, everything works, but with it enabled, it seems that
the usb driver (usb-uhci) is not getting any interrupts. johannes
erdfelt thinks that it's a pci irq routing problem (/proc/interrupts is
showing no interrupts for usb-uhci when apic is enabled) and suggested
talking with the pci irq people.
i eager to help debug this problem and apply any and all test patches to
find fixes. i am pretty sure that greg k-h (greg AT kroah DOT com) is
also willing to do the same. the problem is, we can't get any pci irq
people to look into this. is this a problem with the pci irq routing?
is this a known problem that someone's working on? is it just not worth
the effort? there are already quite a few people on the linux-usb list
who are seeing this problem. i'm sure that when 2.4.0 comes out, a lot
more people will be seeing this problem too. please, let's try to stomp
this out before 2.4.0 and make linux look just that little bit more
shiny. =8]
(sorry for that bit of a rant, but i'm getting just a little bit
frustrated with this long-standing problem.)
thanks,
pete
--
Pete Toscano p:sigsegv@psinet.com w:pete@research.netsol.com
GPG fingerprint: D8F5 A087 9A4C 56BB 8F78 B29C 1FF0 1BA7 9008 2736
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2000-12-22 22:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001222171250.A28612@tesla.admin.cto.netsol.com \
--to=pete@research.netsol.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
Powered by JetHome