From: Peter Horton <pdh@colonel-panic.org>
To: linux-mips@linux-mips.org
Subject: Tulip problems on Qube 2
Date: Mon, 15 Dec 2003 22:19:35 +0000 [thread overview]
Message-ID: <20031215221935.GA31161@skeleton-jack> (raw)
Is anyone looking at the problems with the Tulip network driver on the
Cobalt Qube 2 ?
I've started poking around but am not getting very far ...
The card works okay for a few minutes but then something gets very
confused in the receive ring. If the card is being pinged with packets
once a second it generates a receive interrupt for every packet, but the
first receive ring entry is marked busy so the packet's not passed up.
Once we've received 32 packets the NIC wraps round the receive ring and
the entry we've been waiting on gets marked as full. Now the receive
interrupt removes that last packet and the 31 preceding ones in one go.
Then we stall for another 32 seconds.
It looks like we're loosing some of the NIC's writes to the receive ring
status entries in main memory ...
P.
next reply other threads:[~2003-12-15 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 22:19 Peter Horton [this message]
2003-12-15 22:48 ` Tulip problems on Qube 2 Kumba
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=20031215221935.GA31161@skeleton-jack \
--to=pdh@colonel-panic.org \
--cc=linux-mips@linux-mips.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