From: Oliver Martin <oliver.martin@student.tuwien.ac.at>
To: netdev@vger.kernel.org
Cc: hvr@gnu.org, buytenh@wantstofly.org
Subject: ep93xx_eth PHY problems
Date: Tue, 04 Mar 2008 14:02:15 +0100 [thread overview]
Message-ID: <47CD4857.2060406@student.tuwien.ac.at> (raw)
Hello,
I was having problems with the ep93xx_eth driver: apparently the PHY
auto-negotiated "100/full" with the switch, but the driver didn't care
about it (or is it the other way round?). This led to lots of packets
being dropped under load. Anyway, the patch that was posted last
november (http://marc.info/?l=linux-netdev&m=119520642207001&w=4)
helped.
Now I'm having different problems: When auto-negotiation is enabled, it
sometimes randomly changes the link state:
PHY: 0:01 - Link is Down
PHY: 0:01 - Link is Up - 100/Full
PHY: 0:01 - Link is Up - 100/Half
PHY: 0:01 - Link is Up - 100/Full
PHY: 0:01 - Link is Up - 10/Half
PHY: 0:01 - Link is Up - 100/Full
It could be related to some kind of error handling - often, when this
happens, our test (a simple RFC 862 UDP echo server, see [1]) loses
packets, but the message seems to appear only after the test fails.
If I disable auto-negotiation with ethtool, it first changes to the mode
I choose, but seconds later changes to "1000/Full":
PHY: 0:01 - Link is Up - 100/Full
PHY: 0:01 - Link is Up - 1000/Full
This is obviously impossible, and while it mostly works, it seems to
confuse something (PHY? MAC? driver?), as there seem to be more dropped
packets than with the Cirrus 2.4 driver (on a TS-7260 with the default
TS-Linux).
Maybe some error condition isn't handled properly, causing both the
packet loss and the PHY state change? Of course, I'm just speculating
and it might be something entirely different.
Any ideas?
--
Oliver
[1] http://murli.34sp.com/o/ep93xx-eth/echo/
next reply other threads:[~2008-03-04 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 13:02 Oliver Martin [this message]
2008-03-21 19:22 ` [PATCH] Re: ep93xx_eth PHY problems Oliver Martin
2008-03-26 4:42 ` Jeff Garzik
2008-03-29 18:13 ` Oliver Martin
2008-03-29 18:17 ` Lennert Buytenhek
2008-09-14 2:11 ` Jeff Garzik
2008-09-14 11:47 ` Lennert Buytenhek
2008-09-14 11:58 ` Herbert Valerio Riedel
2008-09-14 12:11 ` Oliver Martin
2008-09-14 12:12 ` Lennert Buytenhek
2008-09-14 12:24 ` Oliver Martin
2008-09-16 12:51 ` Lennert Buytenhek
2008-09-17 9:13 ` Oliver Martin
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=47CD4857.2060406@student.tuwien.ac.at \
--to=oliver.martin@student.tuwien.ac.at \
--cc=buytenh@wantstofly.org \
--cc=hvr@gnu.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).