From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: 8260 FCC enet driver problem
Date: Tue, 30 Sep 2003 17:20:35 +0200 [thread overview]
Message-ID: <000001c38766$68b14d90$5201a8c0@GEG2400> (raw)
Hi,
I use a 2.4.18 Linux kernel on my custom 8260 board with 3 FCC ports.
These 3 ports work fine at 100Mbs half or full duplex.
I connect 2 boards on the first port via a 10Mbs hub.
The ports auto-negotiate and fall into 10Mbs half duplex mode.
A board sends short udp messages as fast as possible to the other one
and vice-versa.
I get the following message and the two ports are locked forever :
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed out.
> Ring data dump: cur_tx c0164220 (full) cur_rx c01641e8.
> Tx @base c0164208 :
> 9c00 0048 018d1ee2
> 9c00 0048 018d15e2
> 9c00 0048 018d1ae2
The PHY devices seem to be well configured.
Does anyone know what are the conditions to fall into this trap ?
Is it a PHY problem, a driver configuration problem or something else ?
Why does the problem not disappear when the traffic is interrupted ?
Only a board reset can reactivate the ports.
Thank you for your help.
Gérard
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-09-30 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:20 Gérard Guével [this message]
2003-10-10 12:25 ` 8260 FCC enet driver problem Steffen Rumler
2003-10-13 19:30 ` Dan Malek
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='000001c38766$68b14d90$5201a8c0@GEG2400' \
--to=gguevel@interfaceconcept.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).