From: Ian Molton <spyro@armlinux.org>
To: linux-kernel@vger.kernel.org
Subject: [USB OHCI] BUG()
Date: Wed, 29 May 2002 02:04:27 +0100 [thread overview]
Message-ID: <20020529020427.6a9cdc92.spyro@armlinux.org> (raw)
Hi.
I wrotew a while ago about an oops I was getting with an OPTi OHCI USB
1.1 card, a BUG() at line 464 in one of the usb-ohci.h, IIRC.
well, I since replaced the card with an NEC USB 2.0 card, (and am using
OHCI mode), and am hitting the same BUG().
Here is a cat /proc/pci (trimmed)
Bus 0, device 10, function 0:
USB Controller: NEC Corporation USB (rev 65).
IRQ 10.
Master Capable. Latency=16. Min Gnt=1.Max Lat=42.
Non-prefetchable 32 bit memory at 0xe0800000 [0xe0800fff].
Bus 0, device 10, function 1:
USB Controller: NEC Corporation USB (#2) (rev 65).
IRQ 12.
Master Capable. Latency=16. Min Gnt=1.Max Lat=42.
Non-prefetchable 32 bit memory at 0xe0801000 [0xe0801fff].
Bus 0, device 10, function 2:
USB Controller: NEC Corporation USB 2.0 (rev 2).
IRQ 5.
Master Capable. Latency=16. Min Gnt=16.Max Lat=34.
Non-prefetchable 32 bit memory at 0xe0802000 [0xe08020ff].
This is starting to look like a real bug, not just a 'crap OPTi' bug.
Oh, one other thing - when using my ADSL modem on this USB card, ping
shows up occasional 'wrong' packets. with 2.4.18, this didnt happen (I
suspect it simply oopsed instead). Does this help?
Anyone here want to suggest some debug code?
Kernel 2.4.19-pre8-ac5
On another note, I need my server up and running - can anyone suggest a
PCI USB card / chipset that actually ***works*** on Linux (preferably
UHCI based as all UHCI stuff I tried so far has worked)?
have I justr been exceptionally unlucky and bought two duff chipsets, or
is Linux OHCI just really flakey ?
reply other threads:[~2002-05-29 0:55 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=20020529020427.6a9cdc92.spyro@armlinux.org \
--to=spyro@armlinux.org \
--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